Repository navigation
docs(changelog): move the client-certificate entry back to Unreleased - #849
Merged
Merged
Conversation
github-actions
Bot
added
size/S
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.
#844 was merged while behind
main, just after the v2.31.0 metadata sync (#848). Its head predated the cut, so the merge placed its Security entry inside the released## [2.30.1]section and left## [Unreleased]empty:[Unreleased]on fix(security): refuse client-certificate flags without a server certificate and key #844's merge and skipped the release (CHANGELOG [Unreleased] section is empty; skipping release), so the fix has not shipped yet.This moves the entry, unchanged, to
[Unreleased] / ### Security.[2.30.1]and[2.31.0]are byte-for-byte what #848 merged; the set of entries in the file is unchanged.This PR only touches
CHANGELOG.md, which the release workflow ignores, so it cuts no release by itself. The fix ships with the next release: either the next merge that ships code, or a manual run of the auto-release workflow after this merges.Same repair as #605.