chore: Add a Release Please manifest. #47
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
copybara/709117873
branch
from
1a1e710 to
84b70bf
Compare
Release please seems to be starting at version 0.1.0 while we've already manually released 0.3.0. I **think** checking in the .release-please-manifest.json with the version set should fix that. The `.json` files in this change were created by running: ``` release-please bootstrap --release-type=python --initial-version=0.3.0 --bump-minor-pre-major --repo-url=amirh/python-genai ``` PiperOrigin-RevId: 709117873
copybara-service
bot
force-pushed
the
copybara/709117873
branch
from
84b70bf to
cf85112
Compare
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.
chore: Add a Release Please manifest.
Release please seems to be starting at version 0.1.0 while we've already manually released 0.3.0.
I think checking in the .release-please-manifest.json with the version set should fix that.
The
.jsonfiles in this change were created by running: