fix(ci): clear temp snowball tree before crates.io publish - #1
Merged
Conversation
cargo publish failed after a successful sync because nested .snowball-src left a dirty working tree. Remove it before publish, write semver-check logs under RUNNER_TEMP, ignore residual log files, and drop the ones accidentally committed on main.
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.
Why
Daily upstream release for
1.20260805.0synced, tested, tagged, and authenticated with crates.io, then failed atcargo publishwith a dirty working tree under.snowball-src(ada/README.md,go/README.md). That left tagv1.20260805.0on GitHub without a crates.io publish.What
.snowball-srcimmediately beforecargo publishcargo semver-checkslogs to$RUNNER_TEMPinstead of the repo rootsemver.out/semver.errand delete the copies accidentally committed on mainNote
This PR does not republish
1.20260805.0. After merge, useworkflow_dispatchwithforceif a same-day re-release is needed; the version step will bump patch when the existing tag is present.