Fix failure to update __version__ #481
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
consideRatio
commented
Jun 25, 2024
| @@ -1,4 +1,4 @@ | |||
| # __version__ should be updated using tbump, based on configuration in | |||
| # pyproject.toml, according to instructions in RELEASE.md. | |||
| # | |||
| __version__ = "4.1.1-0.dev" | |||
| __version__ = "4.2.1-0.dev" | |||
There was a problem hiding this comment.
This is the current version declared in pyproject.toml for tbump, so its just updating it to match.
|
Tests are unrelated and failing in main branch, I'm self merging this minor fix. |
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.
During our release process, the
_version.pyfile wasn't updated as it should been so when inspecting__version__we actually just got4.1.1-0.devin the released package where we expected4.2.0.