ci: allow Rust release retries from existing tags - #4051
Closed
chaokunyang wants to merge 1 commit into
Closed
chaokunyang wants to merge 1 commit into
chaokunyang wants to merge 1 commit into
Conversation
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
2 participants
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.
Apache Fory 1.7.3 Rust publication fails before starting because its immutable tag pins
crates-io-auth-actionv1.0.4, which is no longer on the ASF action allowlist. Main already uses the approved v1.0.5 action.Add a manual release-tag input to the existing Rust publishing workflow so it can run the current approved actions while checking out and publishing the source from the original release tag. The selected tag controls both checkout and version normalization; branch names are rejected. Automatic tag publication uses the same path.
Validation: YAML lint and Prettier checks passed, the shell validation accepts final/RC tags and rejects branch names, and
git diff --checkpassed. The actual crates.io publication will run after this workflow is merged, withtag=v1.7.3.