Add changelog for v1.0.0#113
Merged
consideRatio merged 2 commits intoexecutablebooks:mainfrom Apr 11, 2025
Merged
Conversation
Member
|
IMO go for it. 1.0 shouldn't be the psychological barrier that we all treat it to be. I'd even prefer that we start with 3.0 haha. IMO, bump major versions often! |
Collaborator
|
Go for it! |
Collaborator
Author
|
Thank you all for such quick feedback, I went for it! I ran into various other automation issues, so it led to a few quick patch releases. |
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
3 participants
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.
Ping @blink1073 @minrk @choldgraf @jtpio @manics by virtue of being PyPI package maintainers or recently active in relation to this repo. What do you think - okay to cut 1.0.0? I have preliminary set the release date to 15th April in order to ensure some time for feedback.
Note that I have just self-merged a lot of chore PRs in a burst of effort to get a release out which is very long overdue, the self-merged PRs are all listed in this changelog under the documentation/maintenance/continiuous integration headings.