Re-order changelog entries for 0.9.7 #16344
Merged
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.
Summary
This is mainly on me for not noticing this during the last release but I noticed in the last changelog that there's only 1 bug fix which didn't seem correct as I saw multiple of them so I looked at a couple of PRs that are in "Rule changes" section and the PRs that were marked with the
buglabel was categorized there becauseruleandfixes([pylint] Correct ordering of arguments in fix forif-stmt-min-max(PLR1730) #16080, [flake8-comprehensions]: Handle trailing comma inC403fix #16110, [pyupgrade] Do not upgrade functional TypedDicts with private field names to the class-based syntax (UP013) #16219, etc.)buglabel (but the issue as marked asbug) but only labels like "fixes" ([pydocstyle] Handle arguments with the same names as sections (D417) #16011, [pylint] Do not offer fix for raw strings (PLE251) #16132, etc.)