Write Changelog for 2.4.0 #9847
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
AbstractUmbra
force-pushed
the
update/changelog
branch
from
b3f4324
to
80aecb3
Compare
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.
Summary
This PR attempts to write a Changelog for the features released within the library after the 2.3.2 release.
Going by a historical reference (like reading
whats_new.rstas I added more) I followed the same concepts.This means I did not add typing-only changes, nor did I add documentation-only changes.
I also followed a principle of not adding followup commits to a feature that was released as part of 2.4. I.e. The addition of
discord.Polland all other aspects of that PR were added, but the few followup fix commits were not, as I considered them "part" of the addition. I can rectify this if this is not desired.Checklist