ci(release): cargo publish --allow-dirty (Cargo.lock churn on resolve) - #5
Merged
Conversation
Resolving against the freshly-cloned sibling soap-server plus the now-published 0.1.1 regenerates Cargo.lock during the publish build, tripping the dirty-tree check. Pass --allow-dirty: published contents are governed by the Cargo.toml `include` allowlist, not working-tree state, so the regenerated lock does not leak anything. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #4. The publish build regenerates Cargo.lock (cloned sibling soap-server + now-published 0.1.1), tripping the dirty-tree check.
--allow-dirtyis safe here — theincludeallowlist governs package contents. Merging does not publish; I'll dispatch after merge.