OPSC-17970 Add missing netty upgrade release note#283
Merged
Conversation
annieden
reviewed
Jul 10, 2026
annieden
approved these changes
Jul 10, 2026
annieden
left a comment
annieden
left a comment
Contributor
There was a problem hiding this comment.
added a period at the end of the sentence. commit that and you are good to go.
Minor review update Co-authored-by: annieden <94020405+annieden@users.noreply.github.com>
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
2 participants
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.
OPSC-17970 was missing the doc impact field so it didn't get picked up by the release notes generator. This adds the missing release note.
The opscenter release notes generator has been updated to list all tickets in the release without release notes to make this kind of thing easier to prevent in the future.
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.