Skip to content

feature/tag-guards - #37

Merged
CiaranOMara merged 2 commits into
developfrom
feature/tag-guards
Oct 27, 2026
Merged

CiaranOMara merged 2 commits into
developfrom
feature/tag-guards

Conversation

@CiaranOMara

Copy link
Copy Markdown
Member

No description provided.

The tag workflow moved a major tag to its major version's newest release tag, so deleting the newest version's tag would have taken the major tag back to an older release: as happened to v1, which only a refusal stopped.
A major tag now moves only to a release that descends from where it is, and otherwise stays, with a notice that says so.

A refused move reported only the step's exit code.
Each refusal is now an error with GitHub's message, and a line of the job's summary; the other major tags are still handled, and the step fails at the end.
The back-merge of a release into develop shares the release's tree, and TagBot tags the most recent commit with the registered tree, so it would tag the back-merge rather than master's merge commit.
TagBot's `branch` input names master, whose history TagBot is to search first; until TagBot does, it only sets the release's target.
@CiaranOMara
CiaranOMara merged commit 8aa4856 into develop Oct 27, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant