Tag release: a manual run, for a merge whose push event never arrived - #171
Merged
Merged
Conversation
GitHub ran no workflow at all for the merge of #167 (0d35a90), so v0.6.3rc2 was never tagged, and the workflow had no way to be run by hand. The manual run tags the commit on main that last changed VERSION, which is what the push run would have tagged, and refuses when the tag exists or VERSION is not a release version.
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.
GitHub ran no workflow at all for the merge of #167 (
0d35a90, 2026-09-28 19:48 UTC): not Tag release, and not the Lint and Test jobs that run on every push. Its status page showed no incident. Sov0.6.3rc2was never tagged, and Tag release had only a push trigger, so nothing could run it by hand.This adds
workflow_dispatch. The push path is unchanged and still goes through the shared workflow.The manual run:
mainonly;VERSIONthat is not a release version;mainthat last changedVERSION(first-parent), which is the merge the push run would have tagged, not the branch head.Checked locally against this tree: the version reads
0.6.3rc2, the tag is absent, and the commit found is0d35a90. Four malformed versions are refused.Not tested: the run itself, which can only happen once this is on
main.The same gap is in every repository that calls the shared tagging workflow. Moving the manual path into the shared workflow is filed separately.