Skip to content

Tag stable on every release - #456

Merged
lelia merged 4 commits into
mainfrom
lelia/tag-stable-on-release
Nov 20, 2026
Merged

lelia merged 4 commits into
mainfrom
lelia/tag-stable-on-release

Conversation

@lelia

@lelia lelia commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

socketdev/cli:stable only moved when someone ran Mark Release as Stable (docker-stable.yml) by hand. That hasn't happened since January 2025, so anyone following stable has been on a CLI about ten months old. This project has no separate soak or vetting step for stable to stand for, so it now simply follows latest.

Changes

  • release.yml: the release build tags socketdev/cli:stable alongside latest and socketdev/cli:<version>, so every release, including ones cut without a follow-up step, moves stable.
  • docker-stable.yml: unchanged apart from a header comment. It's now only for pointing stable at a different release, for example to roll back. Since 2.12.0 it retags the published image rather than rebuilding it.
  • docs/ci-cd.md: says latest and stable both point at the newest release, and recommends pinning a version tag for reproducible CI.
  • CHANGELOG.md and version: 2.12.2.

Notes

  • Docker Hub's tag-immutability rule (^\d+\.\d+\.\d+$) covers only version tags, so latest and stable remain overwritable.
  • stable is being moved to 2.12.1 by hand ahead of this, so it's current before the first automatic update.

Fixes CE-510

`stable` only moved when someone ran docker-stable.yml by hand, and it had
not been run since January 2025, so the tag pointed at a CLI about ten
months old. The release build now tags `stable` alongside `latest` and the
version tag. docker-stable.yml stays as a manual way to point `stable` at a
different release, such as rolling back.

Bumps to 2.12.2.
@lelia
lelia requested a review from a team as a code owner November 17, 2026 20:01
@cursor

cursor Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Changes are limited to release workflows, Docker tagging, documentation, and version metadata with no application or security logic touched.

Overview
Each release now pushes socketdev/cli:stable alongside latest and the version tag, so stable tracks the newest image without a manual promotion step. docker-stable.yml is documented as rollback-only (repoint stable at an older release).

Docs and CHANGELOG describe that latest and stable both follow the newest release and recommend pinning socketdev/cli:<version> for reproducible CI. Version bumped to 2.12.2.

Reviewed by Cursor Bugbot for commit 1451dbc. Configure here.

@lelia
lelia temporarily deployed to socket-firewall November 17, 2026 20:01 — with GitHub Actions Inactive
@lelia

lelia commented Nov 17, 2026

Copy link
Copy Markdown
Contributor Author

bugbot run

@cursor cursor 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.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 1451dbc. Configure here.

@lelia
lelia temporarily deployed to socket-firewall November 19, 2026 20:58 — with GitHub Actions Inactive
@lelia
lelia deployed to socket-firewall November 20, 2026 22:28 — with GitHub Actions Active
@lelia
lelia merged commit 9d976e7 into main Nov 20, 2026
33 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.

2 participants