[Release] Update release notes after code freeze #16163
Merged
Conversation
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
jaclync
added
the
Releases
Collaborator
Generated by 🚫 Danger |
itsmeichigo
approved these changes
Sep 23, 2025
Contributor
itsmeichigo
left a comment
itsmeichigo
left a comment
There was a problem hiding this comment.
Thanks for the update!
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.
This PR updates the 23.3 release notes string based on feedback after code freeze #16156 (comment), from a misunderstanding of AI & lack of context from Peacock members.
I'm following the steps in p1758531030419389/1758501339.104309-slack-CC7L49W13 to update the strings. Hopefully the cron job will pick up the updates by the time they are sent for translation on Tuesday p1758558281839089/1758532145.366019-slack-C02AED43D (unsure which time zone).