Name the rolling channel after the branch it comes from - #124
Merged
Conversation
:edge said nothing about where the images came from; :develop does. The target, the workflow and the docs all move with it, so one concept has one name across both registries. Anyone following ghcr.io/...:edge must switch to :develop — the old tag stops being updated rather than disappearing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
the
breaking-change
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
:edgesaid nothing about where the images came from.:developdoes, and it is the name you already know from the branch.Renamed together so one concept keeps one name:
PushEdgePushDeveloppublish-edge.ymlpublish-develop.yml:edge:developBoth registries use it: GHCR on every non-docs push to the trunk, and Docker Hub when the mirror is dispatched.
Docs updated in
README,CLAUDE.md,ci.md,releasing.mdandbranching-and-release.md. The plan underdocs/plans/still says:edgeand is left alone deliberately — it is a dated record of what was planned in August, not live documentation.Labelled
breaking-change: anyone pullingghcr.io/chrison-dev/krautwatch-*:edgehas to switch tags. The old tag is not deleted, so nothing breaks immediately — it simply stops being updated, which is the failure mode worth mentioning in the release notes. Realistically that is nobody yet; the channel is a few days old../build.sh Testgreen: 492 passing.