ci: recover immutable-tag releases through protected main - #78
Merged
Conversation
Manual recovery checks out the existing signed tag while running reviewed workflow tooling from main. Upgrade cargo-semver-checks to 0.50.0 so the pinned nightly rustdoc format is supported.
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.
Summary
This unblocks the existing immutable
v0.8.0tag at2c76ca497a7b4f4acf72062a07267d29fe69aeae; the first Release run failed before publication because cargo-semver-checks 0.48.0 only understood rustdoc JSON through v57.Validation
just push-fulljust check-actionscargo semver-checks --package rscrypto --all-featureswith cargo-semver-checks 0.50.0git diff --checkNo release change fragment: this changes maintainer release tooling only.