docs(release_notes): promote v1.94.0 to stable - #701
Merged
Conversation
Renames the v1.94.0rc1 folder to v1.94.0 and moves the title, slug, date, Docker tag, pip install, and Full Changelog range onto the stable form. The rc1 notes predated rc2 and rc3, so this folds in the 27 PRs that landed between rc1 and the stable cut: the new beta Cost Optimization page and its follow-up layout, axis and description fixes, the tool spend daily rollup with a 30-day cap on /v1/tool/spend, org spend attribution for team-linked credentials minted without an org_id, prompt compression saved tokens in the daily aggregates, the temp_budget_increase fixes, CLI SSO sessions shared across workers, the model_armor None metadata fix, the Fireworks Content-Type 415 fix, bedrock_tags on batch jobs, and the flagged dependency refresh. The ownership roll-up moves to 263 and the changelog landing page now leads with v1.94.0. Also clears stale 1.94.0 references elsewhere in the docs. The Rust gateway page cited a v1.94.0-stable tag that does not exist under the current PEP 440 naming, users.md still described skip_user_budget_on_team_key as pending when it shipped in the release, and the budget_reset_time notes anchored to v1.94.0rc1 rather than the stable version it now trails.
|
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.
Moves the release notes out of rc now that 1.94.0 is released. The
v1.94.0rc1folder becomesv1.94.0, and the title, slug, date, Docker tag, pip install, and Full Changelog range all move onto the stable form (v1.93.0...v1.94.0).The rc1 notes predated rc2 and rc3, so this folds in the 27 PRs that landed between rc1 and the stable cut. The largest addition is the beta Cost Optimization page, which had no mention at all in the rc notes and does not exist in 1.93.0, so it gets a Key Highlight plus its own feature and bug subsections covering the spend-by-tool and cache leakage views, the four configuration tabs, the beta badge, and the layout, axis and page-description fixes. The rest slot into existing sections: the tool spend daily rollup with a 30-day cap on
/v1/tool/spend, org spend attribution for team-linked credentials minted without anorg_id, prompt compression saved tokens in the daily aggregates, the threetemp_budget_increasefixes, CLI SSO sessions shared across workers, the model_armorNonemetadata fix, the FireworksContent-Type415 fix,bedrock_tagson batch jobs, and the flagged dependency refresh. The ownership roll-up goes from 236 to 263 and the changelog landing page now leads with v1.94.0.Four stale 1.94.0 references elsewhere in the docs are corrected in the same pass. The Rust gateway page cited a
v1.94.0-stabletag that does not exist under the current PEP 440 naming and described the flag in future tense;users.mddescribedskip_user_budget_on_team_keyas coming in the release candidate when it shipped in the release, which matters because it is the setting behind the breaking-change admonition; and the twobudget_reset_timenotes anchored tov1.94.0rc1rather thanv1.94.0. That field is genuinely still unreleased, so only the anchor changed.Two things worth a reviewer's eye. The end-to-end testing section still links the rc1 report, since that is the only run in the repo; the surrounding sentence now says the run was executed against the release candidate rather than implying it covered the stable build, and swapping in a stable-build run would be better if one exists. The roll-up total is an estimate rather than a canonical recount, consistent with how prior promotions have handled it.