Skip to content

Promote main on a branch push, latest on a release tag - #31

Merged
fatherlinux merged 2 commits into
mainfrom
latest-means-newest-release
Nov 7, 2026
Merged

fatherlinux merged 2 commits into
mainfrom
latest-means-newest-release

Conversation

@fatherlinux

Copy link
Copy Markdown
Member

Summary

One floating tag moves per run, and which one is the point. latest is now the newest release; main is the branch. Implements constitution 1.33.0 (crunchtools/constitution#95).

Before this, a push to main moved latest — which is what 44 of the 51 auto-updating units on gloval pull. On 2026-11-07 that put unreleased trentina 6.11.0 into production at 02:01:53 through podman-auto-update, where it climbed to the unit's 4g cap and was SIGKILLed. Nothing had asked for it and nothing was watching.

Also fixed

The backwards-move guard now asks about whichever tag the run moves, rather than always about latest. A re-run of an old release tag must not demote latest any more than a re-dispatched old commit may demote main — and before this the release half of that was unguarded.

The gates are unaffected

bin/sdlc resolves its image from the repo's IMAGE_TAG file, which the pinned rev: clone carries. Every consumer already pulls a version tag (:0.5.1 today) and never latest, so no repo's push gate changes behaviour.

Test plan

  • container.yml parses; promote job's steps verified
  • Tag selection checked against refs/heads/main, refs/tags/v0.5.3, refs/pull/9/merge, refs/tags/nightly — only a v* tag selects latest
  • Push gate green locally (ruff, shellcheck, Gourmand, Gatehouse)
  • The real proof is the next release: a push to main must move :main and leave :latest where it is

RT#1559

🤖 Generated with Claude Code

https://claude.ai/code/session_01R7Y1jfBgAyvK9xarny6EHx

One floating tag moves per run, and which one is the point. `latest` is
now the newest RELEASE; `main` is the branch. Constitution 1.33.0.

Before this, a push to main moved `latest`, which is what 44 units
across the fleet pull. On 2026-11-07 that put unreleased trentina
6.11.0 into production at 02:01 through podman-auto-update, where it
climbed to the unit's 4g cap and was SIGKILLed. Nothing had asked for
it and nothing was watching.

The backwards-move guard now asks about whichever tag this run moves,
rather than always about `latest`. A re-run of an old release tag must
not demote `latest` any more than a re-dispatched old commit may demote
`main`, and before this the release half of that was unguarded.

The gates are unaffected: `bin/sdlc` resolves its image from the repo's
IMAGE_TAG file, so every consumer already pulls a version tag and never
`latest`.

RT#1559

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R7Y1jfBgAyvK9xarny6EHx

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

Full review.

1 finding(s) dropped: their evidence is not in the diff.

Gatehouse, on the same change in mcp-gemini: a `v*` test admits
`v1.2.3-rc.1`, so a release candidate could move `latest` away from the
newest stable release -- the one thing this change exists to prevent.

A prerelease is not the branch either, so it now moves NO floating tag
and publishes its version tags alone. SemVer puts every prerelease
identifier after a hyphen, so `v*-*` is the whole test.

RT#1559

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R7Y1jfBgAyvK9xarny6EHx

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

Reviewed 1 commit since 7d87b4b (incremental).

1 finding(s) dropped: their evidence is not in the diff.

@fatherlinux
fatherlinux merged commit 978246b into main Nov 7, 2026
10 checks passed
@fatherlinux
fatherlinux deleted the latest-means-newest-release branch November 7, 2026 16:42
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