Release for 0.2.0 - #13
Merged
Merged
Conversation
handlename
force-pushed
the
tagpr-from-0.1.0
branch
from
May 16, 2026 09:04
851d1e0 to
2f90bda
Compare
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.
This pull request is for the next release as 0.2.0 created by tagpr. Merging it will tag 0.2.0 to the merge commit and create a GitHub release.
You can modify this branch "tagpr-from-0.1.0" directly before merging if you want to change the next version number or other files for the release.
How to change the next version as you like
There are two ways to do it.
What's Changed
Full Changelog: 0.1.0...tagpr-from-0.1.0