Repository navigation
Conversation
`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.
PR SummaryLow Risk Overview Docs and CHANGELOG describe that Reviewed by Cursor Bugbot for commit 1451dbc. Configure here. |
|
bugbot run |
There was a problem hiding this comment.
✅ 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.
socketdev/cli:stableonly moved when someone ran Mark Release as Stable (docker-stable.yml) by hand. That hasn't happened since January 2025, so anyone followingstablehas been on a CLI about ten months old. This project has no separate soak or vetting step forstableto stand for, so it now simply followslatest.Changes
release.yml: the release build tagssocketdev/cli:stablealongsidelatestandsocketdev/cli:<version>, so every release, including ones cut without a follow-up step, movesstable.docker-stable.yml: unchanged apart from a header comment. It's now only for pointingstableat 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: sayslatestandstableboth point at the newest release, and recommends pinning a version tag for reproducible CI.CHANGELOG.mdand version: 2.12.2.Notes
^\d+\.\d+\.\d+$) covers only version tags, solatestandstableremain overwritable.stableis being moved to 2.12.1 by hand ahead of this, so it's current before the first automatic update.Fixes CE-510