Release workflow: retry builds the tagged commit, wherever main is - #48
Merged
Merged
Conversation
retry insisted that the version commit is HEAD, but main moves on as soon as anything else is merged, as happened between the failed 0.1.18 release and its retry. The retry now checks out the tag of the version in lib/*/version.rb and rebuilds that commit. Co-Authored-By: Claude Fable 5.1 <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.
The retry of 0.1.18 refused with
retry only finishes a release whose version commit v0.1.18 is HEAD:mainhad moved on by the merge of the trusted-publishing change, which had to land before any retry could publish. That guard was too strict. A retry now checks out the tag of the version inlib/*/version.rband rebuilds that commit, wherevermainis, then pushes the gem if RubyGems.org is still missing it and creates the GitHub release if it is still missing.The dry run on this branch stops after the build, as before. The push that merges this triggers a dry run on
mainthat performs the OIDC exchange, so it doubles as the check of the trusted publisher. After that, Actions → Release →retryfrommainfinishes 0.1.18.🤖 Generated with Claude Code