fix(ci): absorb the v prefix a release dispatch is typed with - #103
Merged
Conversation
|
Merged
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
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 release workflow reads the version from a dispatch field and looks the
changelog section up by its heading,
## [1.8.11]. Typing the tag insteadof the version -
v1.8.11- makes it search for## [v1.8.11], whichcannot exist, and the run fails on:
That is the guard doing its job: it refuses to tag and publish a version
whose notes it cannot find. But the field asks for a bare number while the
thing everyone has in mind is the tag, so the mistake is a reflex, and it
costs a red run in the history of a public repository (it happened on
2026-07-30, fourteen seconds after
release: 1.8.11was merged).The prefix is now absorbed once, in the step that already resolves the
target commit, and both later steps read the normalised value. The field
description says so instead of asking the reader to remember it.
Nothing else changes: a dispatch on
1.8.19behaves exactly as before, andthe workflow stays idempotent on a version already released.