Repository navigation
docs(release_notes): add v1.101.1 release notes - #1607
Closed
yuneng-berri wants to merge 1 commit into
Closed
yuneng-berri wants to merge 1 commit into
yuneng-berri wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Superseded by #1935, which covers everything v1.101.1 actually shipped, not only the two fixes drafted here |
This branch was successfully deployed
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.
Documents the pending
v1.101.1on thestable/1.101.xline. That version was already cut by PR #41704 but has never been built or published, so nothing on this line has shipped sincev1.101.0The release will contain two fixes: the Bedrock Converse
maxTokensfloor backported in PR #42332, and the wildcard-license auto-router fix already merged to the line in PR #41698Do not merge this until
v1.101.1actually builds and publishes. If the release is re-cut to a different version, this note has to move with it; thev1.90.2re-cut is the precedent for that riskOne open question changes this note: if
v1.101.1goes out as a Docker-only release, it needs the Docker-only info block that thev1.99.2note carries, and the Pip tab removed. It is currently written for a normal release that publishes to both