ci: pin release tag_name's target_commitish to the triggering commit - #150
Merged
so5 merged 1 commit intoSep 23, 2026
Conversation
Same fix as RIKEN-RCCS#148 on main, backported here: without an explicit target_commitish, softprops/action-gh-release's tag_name creates a new tag defaulted to the repository's default branch (main), not the branch this workflow actually ran on - silently mis-targeting this branch's release tags at main instead of maintenance2026's own commits. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C3jKNM1qubomM8UTRdkEWu
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
Backports #148's fix to
maintenance2026's own copy ofbuild_and_deploy.yml: without an explicittarget_commitish,softprops/action-gh-release'stag_namecreates a new tag defaulted to the repository's default branch (main), not the branch this workflow actually ran on - which silently mis-targeted this branch's release tag atmaininstead ofmaintenance2026's own commit (caught right after backporting the release-labeling scheme in #147).Change
Add
target_commitish: ${{ github.sha }}to the release step.🤖 Generated with Claude Code
https://claude.ai/code/session_01C3jKNM1qubomM8UTRdkEWu