Update RELEASE.md to use tbump#673
Merged
Merged
Conversation
consideRatio
force-pushed
the
pr/use-tbump
branch
from
e244f53 to
2d65473
Compare
Collaborator
Author
|
I'll go for a merge and create a new release to get #672 out. |
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
1 participant
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.
From manually needing to update, commit, tag, and push three files with version fields - we now do it all with a tbump command. This command will also summarize clearly what it will do via
tbump --dry-run <version>as also suggested in the REALEASE.md file before one does it without --dry-run.And, the config on what files to update etc are nicely located into a pyproject.toml file.