Skip to content

ci(release): cargo publish --allow-dirty (Cargo.lock churn on resolve) #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jhogendorn merged 1 commit into from
Jun 3, 2026
Merged

ci(release): cargo publish --allow-dirty (Cargo.lock churn on resolve) #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,11 @@ jobs:
env:
CARGO_REGISTRY_TOKEN: ${{ steps.crates-auth.outputs.token }}
run: |
if cargo publish 2>publish.err; then
# --allow-dirty: resolving against the cloned sibling soap-server + the
# now-published version regenerates Cargo.lock, which would otherwise trip
# the dirty-tree check. Published contents are governed by the Cargo.toml
# `include` allowlist, not the working-tree state, so this is safe.
if cargo publish --allow-dirty 2>publish.err; then
cat publish.err
echo "Published v${{ steps.ver.outputs.version }} to crates.io."
elif grep -qiE "already (exists|uploaded)|is already uploaded|crate version .* is already" publish.err; then
Expand Down
Loading