ci: release-please setup with snapshot and release builds #3
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
ttschampel
previously approved these changes
Mar 14, 2024
ttschampel
reviewed
Mar 15, 2024
ttschampel
approved these changes
Mar 15, 2024
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.
This pr introduces the github action for release-please. It also separates out checks and releases.
The way this works is release-please leverages the commit messages to build a release pr that will update
The settings introduced here mimic the google-cloud-java repo because release-please was a little confusing with all the different java release-types.
Once a release is merged into main release-please will cut a tag then follow up with a snapshot pr that we can merge in to prepare for the next version.