chore: open the 0.4.0 development cycle - #35
Merged
Merged
Conversation
Bump pyproject.toml and uv.lock to 0.4.0.dev0 now that v0.3.0 is tagged and published, matching the post-release bump done after 0.2.0.
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.
Summary
Post-release housekeeping: v0.3.0 is tagged and published to PyPI, so
mainmoves on to the next development cycle.
pyproject.toml/uv.lock:0.3.0->0.4.0.dev0(PEP 440 canonical dev form)Same pattern as the bump to
0.3.0.dev0that followed the 0.2.0 release (#32).