-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconcile dev
after merge to main
for v1.32.0
#3967
Merged
Conversation
This file contains 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
Co-authored-by: Chandrika Srinivasan <chandrikas@users.noreply.github.com>
This PR: - Calls out the router GA version for `persisted_queries` - Cleans up terminology ("preregistered" -> "registered", etc.)
Proposed edits to changelog for 1.32.0 Co-authored-by: Geoffroy Couprie <apollo@geoffroycouprie.com>
> **Note** > **This particular PR must be true-merged to `main`.** * This PR is only ready to review when it is marked as "Ready for Review". It represents the merge to the `main` branch of an upcoming release (version number in the title). * It will act as a staging branch until we are ready to finalize the release. * We may cut any number of alpha and release candidate (RC) versions off this branch prior to formalizing it. * This PR is **primarily a merge commit**, so reviewing every individual commit shown below is **not necessary** since those have been reviewed in their own PR. However, things important to review on this PR **once it's marked "Ready for Review"**: - Does this PR target the right branch? (usually, `main`) - Are the appropriate **version bumps** and **release note edits** in the end of the commit list (or within the last few commits). In other words, "Did the 'release prep' PR actually land on this branch?" - If those things look good, this PR is good to merge!
CI performance tests
|
abernix
approved these changes
Oct 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to the v1.32.0 being officially released, bringing version bumps and changelog updates into the
dev
branch.