documentation: move policy warning to v1.13.2 section #24997
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
Poor timing with documentation updates meant this was in the 1.13.1 section, but the bug is present in v1.13.2 as well. Signed-off-by: Casey Callendrello <cdc@isovalent.com>
squeed
added
the
release-note/misc
maintainer-s-little-helper
bot
added
backport/1.13
|
note: this isn't really a backport, per se, just a tweak of the upgrade notes. |
joestringer
approved these changes
Apr 20, 2023
|
Tangential to this PR, but the updated file seems to hit a gap in Codeowners and did not trigger the Line 323 in a459b33 Do we want to fix this situation? |
|
Scratch that comment, @michi-covalent made me aware that codeowner file is different for stable branches, which we are merging into. You can disregard. |
ldelossa
approved these changes
Apr 20, 2023
|
docs-only change, docs target passed, tophat review in. Can be merged. |
joestringer
added
the
ready-to-merge
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.
Poor timing with documentation updates meant this was in the 1.13.1 section, but the bug is present in v1.13.2 as well.