chore: init release-please version to 0.8.1 - #171
Merged
Conversation
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
2 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.
Purpose of this PR
The release PR #170 resets the version to 0.1.0 as this is the default for release-please. With this change here, release-please should correctly realize that the last released version is 0.8.1. (In the future, release-please will update the manifest automatically, so this here is a one-time action.)
Moreover, configure release-please so that it doesn't include the branch name in the PR title, and finally also update the uv.lock file (which release-please doesn't do automatically googleapis/release-please#2561).
Type of change
(Make sure to delete from the Type-of-change list the items not relevant to your PR)
Checklist:
pyproject.tomlfile accordingly