The changelog feed starts with the public repository: beta keeps 0.200.0, stable starts empty - #5
Merged
Merged
Conversation
…0.0, stable starts empty The feed carried the private repository's whole history (120 beta, 17 stable entries, 2.7 MB). The public repository begins at 0.200.0, so the feed does too: - beta keeps only 0.200.0, the one version published from here; promote refuses a version without a beta entry, so it has to stay. - stable starts empty; promote.yml already treats that as the first stable (prev-stable empty => 0.0.0), and the website falls back to beta until then. Without this, promoting 0.200.x would aggregate 92 items from 0.67-0.103. - changes/stable/0.63.0 and 0.66.0 are removed: curated rollups of promotions that already happened, read only if those versions were promoted again. The earlier history stays in the private nxsflow/nexus-flow-archive. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cabcookie
added
the
skip-changelog
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
release-notes.json: beta keeps only0.200.0; stable becomes[](2.7 MB → 2 KB).changes/stable/0.63.0/andchanges/stable/0.66.0/removed.Why
The public repository started history-free at 0.200.0; the feed still carried the private repository's full history (120 beta, 17 stable entries). The earlier history stays in the private
nxsflow/nexus-flow-archive.changelog assert-beta/promoterefuse a version without a beta entry (xtask/src/changelog.rsassert_beta_entry).promote.ymlalready handles a first stable (prev-stableempty ⇒0.0.0), andcontent/lib/content.mjsfalls back to the beta ring until then. With the old 0.66.0 stable entry in place, promoting 0.200.x would have aggregated 92 items from 0.67–0.103.No code, schema, test or workflow reads the historical entries (content tests use their own fixtures; self-update reads the S3 manifest, not the feed).
skip-changelog: this changes the changelog feed itself, not what a user gets from the product.🤖 Generated with Claude Code