ci(release): drop alpha channel, publish stable to latest#281
Merged
Conversation
The project only needs two release streams: beta prereleases and stable releases. Remove the alpha image channel and reshape the publish flow so a bare version tag (e.g. v1.0.0) is treated as a stable release: - Docker channel tags: `-beta.` tags push the `beta` channel; tags with no pre-release suffix push `latest`. The exact version tag is always pushed regardless. - The release-kit job now runs for any `v*` tag (not just beta) and marks the GitHub release as a prerelease only when the tag carries a suffix, so stable tags produce a full (non-pre) release with the release kit.
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
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.
Simplifies the release streams to just beta (prerelease) and stable, per project scope — alpha is unnecessary overhead for a project this size.
Changes to
publish.ymlalphachannel.-beta.tags publish thebetachannel; version tags with no pre-release suffix (e.g.v1.0.0) publishlatest. The exact version tag is always published.release-kitnow runs for anyv*tag (previously beta-only). The GitHub release is markedprereleaseonly when the tag carries a suffix, so a bare version tag yields a full stable release with the release-kit archive attached.Why now
Without this, a future stable tag would have (a) landed images on the
alphachannel and (b) skipped release creation entirely, since both were gated on-beta.. This unblocks cutting the first stable release.Verification
publish.ymlparses as valid YAML; job graph unchanged (publish→release-kit).-beta.tags still publishbeta+ a prerelease.