docs(release_notes): promote v1.96.0 to stable - #848
Merged
Conversation
Renames the v1.96.0rc1 folder to v1.96.0 and moves the title, slug, date, Docker tag, pip install, and Full Changelog range onto the stable form. The changelog landing page now leads with v1.96.0. The breaking changes move into a :::danger admonition, and the team-key budget revert drops out of that list. It shipped in v1.95.0 by backport #35299, so the v1.95.0 notes already carry it in their own callout, and announcing it twice would read as two separate changes. Ancestry alone says otherwise because the backport carries a different SHA, so this was confirmed by code: skip_user_budget_on_team_key is already absent at v1.95.0. The other two breaking changes were checked the same way and do first ship here. The Full Changelog link resolves once the v1.96.0 tag is cut. The stable image is already published and was built from the rc/1.96.0 tip, but the tag and GitHub release do not exist yet.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Promotes the v1.96.0 release candidate notes to stable, following the shape of PR #744.
Renames
release_notes/v1.96.0rc1torelease_notes/v1.96.0and swaps the title, slug, date, Docker tag, pip version, and Full Changelog range onto the stable form. The changelog landing page now leads with v1.96.0 and gains its row in the recent-releases table.Two edits beyond the mechanical rename. The breaking changes move from a
### Breaking changessubsection into a:::dangeradmonition placed between the deploy block and Key Highlights, which is what this repo's CLAUDE.md asks for and what the v1.95.0 stable notes already do. The team-key budget revert (PR #35271) drops out of that list because it shipped in v1.95.0 by backport, so the v1.95.0 notes already carry it in their own callout and announcing it twice would read as two separate changes. Ancestry alone reports it as absent from v1.95.0 since the backport carries a different SHA, so this was confirmed by code instead:skip_user_budget_on_team_keyis already gone at that tag. The other two breaking changes were checked the same way and do first ship here.One thing to know before merging: the
v1.96.0git tag and GitHub release do not exist yet, so the Full Changelog compare link will 404 until the tag is cut. The stable image is published and resolves on GHCR, built from therc/1.96.0tip.Not included, since the ask was a rename. The line picked up two content PRs after the rc tag, PR #35835 and PR #35844, plus a dependency-pin refresh, all through PR #36294. The v1.95.0 promotion folded its equivalent two PRs into the notes and moved the roll-up total. Happy to do the same here if you want the roll-up to read 153 instead of 151.