docs(release): standardize release notes and artifact lists - #700
Merged
Merged
Conversation
|
✅ OpenCodeReview: Review skipped: no items were selected. |
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
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.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
⚠️ LimitationsbeforeOtherin release notes and place image and chart inventories inAppendix.Which issue(s) this PR links to:
None
Special notes for your reviewer:
make lint docs,RACE=false make test(the CI unit-test mode), andgit diff --checkpassed.make testwith the race detector found a pre-existing data race inTest_k8sCache_TamperedSecretIsLoggedAsKeyValuePairs: the test sets the global klog logger while a background reflector reads it. The same race reproduced on unchangedmainwith the failing shuffle seed.quick_validate.pyin a temporary copy without the repository's pre-existingdisable-model-invocationfrontmatter key, which that generic validator does not recognize.Does this PR introduce a user-facing change?