chore(release-notes): promote 0.200.0 to stable - #6
Merged
Merged
Conversation
The promotion itself ran (promote.yml run 36309436401: S3 copy, stable manifest, sidecars verified), but the release event runs the workflow as of the tag, and v0.200.0 predates PR #3: its best-effort step pushed the feed straight to main and the ruleset declined it. This is that same entry, regenerated locally with `cargo xtask changelog promote 0.200.0` (same 17+/1- diff as the rejected commit). 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.
The stable feed entry for 0.200.0.
The promotion itself succeeded (promote.yml run 36309436401: server-side copy to stable,
manifests/stable.jsonwritten, all stable sidecars verified). Its feed step did not land: areleaseevent runs the workflow as of the tag, andv0.200.0predates #3, so the old best-effort step pushed the feed straight tomainand the ruleset declined it (GH013: Changes must be made through a pull request).This commit is that entry, regenerated locally with
cargo xtask changelog promote 0.200.0— the same 17+/1− diff as the rejected commit. Every later tag carries the PR-based feed step from #3.Merging refreshes the public changelog through
publish-content.yml.🤖 Generated with Claude Code