Merged
Conversation
I pre-populated it with blog post entries since mypy 1.0
ilevkivskyi
approved these changes
Oct 17, 2023
Member
ilevkivskyi
left a comment
There was a problem hiding this comment.
I though that every release would be in its own file. But not really a preference.
Member
|
If they are going to be in one file, perhaps we could add a table of contents to make it easier to navigate to release notes for specific releases? Otherwise looks good! |
Collaborator
Author
|
I think okay to not have explicit table of contents... folks can just use the Github outline on the rhs which is basically a ToC |
Closed
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.
I pre-populated it with blog post entries since mypy 1.0. There might be some markdown or backslashes that are borked, feel free to push to this PR if you notice anything.