Skip to content

Stop publishing a moving 0.0 tag for v0.0.x releases - #71

Merged
Ilyes512 merged 2 commits into
mainfrom
fix/no-moving-0-0-tag
Sep 18, 2026
Merged

Ilyes512 merged 2 commits into
mainfrom
fix/no-moving-0-0-tag

Conversation

@Ilyes512

Copy link
Copy Markdown
Member

Summary

  • merge-go-cli.yml no longer publishes the {{major}}.{{minor}} tag for v0.0.* tags — a 0.0 tag would move across releases that are free to break.
  • Mirrors the existing guard that already skips the bare {{major}} tag under v0.*.
  • v0.5.3 still publishes 0.5; patches within 0.5.x are expected to be compatible.
  • Documented the rule in docs/go-cli.md.

`{{major}}` is already withheld for `v0.*` because a moving `1` promises
compatibility that semver does not make below 1.0. The same argument applies one
level down: under `v0.0.*` every release is free to break, so a moving `0.0` is
a promise nothing backs.

Guards `{{major}}.{{minor}}` on the tag not starting `v0.0.`, mirroring the
existing `{{major}}` guard. `v0.5.3` still publishes `0.5`, since patches within
`0.5.x` are expected to be compatible.

Prereleases are unaffected — metadata-action already collapses every semver
pattern to the full version for them, so they never produced `0.0` to begin
with.
@Ilyes512
Ilyes512 merged commit 80181c1 into main Sep 18, 2026
1 check passed
@Ilyes512
Ilyes512 deleted the fix/no-moving-0-0-tag branch September 18, 2026 22:18
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