Skip to content

ci: pin release tag_name's target_commitish to the triggering commit #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
so5 merged 1 commit into from
Sep 23, 2026
Merged

ci: pin release tag_name's target_commitish to the triggering commit #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/build_and_deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,11 @@ jobs:
wheel_docker.tar.gz
source.tar.gz
tag_name: ${{ env.VERSION_NUMBER }}
# without this, the GitHub API creates a brand-new tag against the
# repository's default branch (main) regardless of which branch this
# workflow actually ran on - a maintenance/beta build's tag would
# silently point at main instead of its own branch.
target_commitish: ${{ github.sha }}
name: "${{ env.TITLE_PREFIX }} ${{ env.VERSION_NUMBER }}"
body: "release for ${{ github.ref_name }} @ ${{ github.sha }} (${{ env.VERSION_NUMBER }})"
# only the main line ever takes the "Latest" badge and the
Expand Down
Loading