chore(publish): label channel/bundle releases as auto-managed pre-releases#32
Merged
Merged
Conversation
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.
What
Future
publish.ymlruns now create thechannel-<name>andbundle-<digest>releases with clearer, self-describing titles and as pre-release / not-latest,
so they no longer claim the repo's Latest badge or read like version releases.
channel-<name>-> title "Signed rules channel:<name>(auto-managed)",--prerelease --latest=falsebundle-<digest>-> title "Rules bundle<digest>(content-addressed)",--prerelease --latest=falseWhy
These releases are machine-addressing artifacts the engine fetches by tag, not
human version releases. Before this, the newest channel pointer grabbed the
Latest badge (misleading) and the bare "Channel: staging" / "Rules bundle …"
titles looked like real releases. A pre-release can never be "Latest", so the
real semver release (
v0.1.0) keeps that badge.No engine impact
Tags (
channel-<name>,bundle-<digest>) and asset filenames are unchanged, sonothing the engine resolves changes. Purely the release title + the
latest/prerelease metadata, which the engine never reads.
The already-published
channel-staging,channel-production, andbundle-…releases were retro-labeled the same way out of band; this just makes every
future publish land consistently.