Skip to content

fix(release): use workspace-relative dist paths for cross-platform staging - #34

Merged
ryanleecode merged 2 commits into
masterfrom
fix/windows-workspace-staging-path
Aug 23, 2026
Merged

fix(release): use workspace-relative dist paths for cross-platform staging#34
ryanleecode merged 2 commits into
masterfrom
fix/windows-workspace-staging-path

Conversation

@systemfsoftware-maker

Copy link
Copy Markdown
Collaborator

Fixes Windows runner artifact upload failure () by using workspace-relative directories across all runners.

Switching --out-dir from an absolute runner.temp path to a workspace-relative
dist/ path introduced a regression on ALL five platforms, not just Windows:
tar is spawned with cwd=binDir, so a relative archive path resolved against
the target dir instead of the invocation dir.

Reproduced locally with a fake bin dir and a relative --out-dir:
  tar (child): dist/release-tarball-linux-x64/...tar.gz: Cannot open: No such
  file or directory
  tar failed with exit code 2

resolve() the out-dir before joining. Re-probed: the archive now lands at the
expected workspace-relative path and contains exactly the `comment-checker`
member, which is what the publish-side cross-check extracts.
@ryanleecode
ryanleecode merged commit 446b7b7 into master Aug 23, 2026
3 checks passed
@ryanleecode
ryanleecode deleted the fix/windows-workspace-staging-path branch August 23, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants