Pin release.yml checkout ref to refs/tags/<tag_name> on workflow_dispatch - #156
Merged
Conversation
…atch
When workflow_dispatch was invoked with a branch name (e.g. "main"),
actions/checkout would silently resolve it as a branch ref and later
steps that assume HEAD is a release tag (git describe --tags
--exact-match HEAD, gh release create --verify-tag, etc.) would fail
with confusing errors. Resolve inputs.tag_name via format('refs/tags/{0}',
inputs.tag_name) in both the release and nuget-publish jobs so a branch
name now fails the checkout step itself instead of reaching the
tag-assumed downstream logic.
https://claude.ai/code/session_01EynRk1KiNDypBTkzJgwfVT
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.
When workflow_dispatch was invoked with a branch name (e.g. "main"),
actions/checkout would silently resolve it as a branch ref and later
steps that assume HEAD is a release tag (git describe --tags
--exact-match HEAD, gh release create --verify-tag, etc.) would fail
with confusing errors. Resolve inputs.tag_name via format('refs/tags/{0}',
inputs.tag_name) in both the release and nuget-publish jobs so a branch
name now fails the checkout step itself instead of reaching the
tag-assumed downstream logic.
https://claude.ai/code/session_01EynRk1KiNDypBTkzJgwfVT