Skip to content

ci: pass --allow-dirty to cargo package/publish#13

Merged
singaraiona merged 1 commit into
mainfrom
ci/allow-dirty-publish
May 1, 2026
Merged

ci: pass --allow-dirty to cargo package/publish#13
singaraiona merged 1 commit into
mainfrom
ci/allow-dirty-publish

Conversation

@singaraiona
Copy link
Copy Markdown
Contributor

Fixes the failure observed on the dry-run dispatch of PR #12's merge commit. The CI vendor step clones rayforce into a gitignored vendor/, so cargo package sees the resulting tree as untracked-and-dirty and refuses without --allow-dirty. That flag is correct for our flow: the source of truth is upstream rayforce plus .rayforce-version, not the committed tree.

Verified by reading the failed dry-run log (run 25221481492); after merge, re-run the dry-run dispatch to confirm green before tagging v0.2.0.

The CI vendor step clones rayforce into vendor/rayforce/ at run
time, but vendor/ is gitignored (the source of truth lives in
upstream rayforce + .rayforce-version, not the committed tree).
cargo package would otherwise refuse to ship what it sees as
'uncommitted changes' from those untracked files.

Caught by the dry-run dispatch on PR #12's merge commit; the
workflow exited with status 101 listing every vendor/rayforce/
file as untracked.
@singaraiona singaraiona merged commit 5d38ec1 into main May 1, 2026
1 check passed
@singaraiona singaraiona deleted the ci/allow-dirty-publish branch May 1, 2026 16:02
singaraiona added a commit that referenced this pull request May 1, 2026
The CI vendor step clones rayforce into vendor/rayforce/ at run
time, but vendor/ is gitignored (the source of truth lives in
upstream rayforce + .rayforce-version, not the committed tree).
cargo package would otherwise refuse to ship what it sees as
'uncommitted changes' from those untracked files.

Caught by the dry-run dispatch on PR #12's merge commit; the
workflow exited with status 101 listing every vendor/rayforce/
file as untracked.

Co-authored-by: Anton <anton.kundenko@gmail.com>
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.

1 participant