ci: Release Please file for gcp-lts-bom and dependencies modules#2420
Merged
suztomo merged 2 commits intoGoogleCloudPlatform:masterfrom Oct 27, 2025
Merged
ci: Release Please file for gcp-lts-bom and dependencies modules#2420suztomo merged 2 commits intoGoogleCloudPlatform:masterfrom
suztomo merged 2 commits intoGoogleCloudPlatform:masterfrom
Conversation
The bootstrap-sha points to GoogleCloudPlatform@8eb8233. This is the parent commit of "Release 1.5.15-dependencies: Bumping to next version post release (GoogleCloudPlatform#2408)". LTS BOM 9.0.1 release happened after that. New tag format is "<component>-v<version>". For example "gcp-lts-bom-v9.0.1" and "dependencies-v1.5.15".
suztomo
changed the title
Becasue there was an independent step to sign artifaccts in the previous releases using Rapid, the pom.xml files didn't need to have GPG signing configurations. With new release setup, there's no independent step to sign artifacts. We need to use maven-gpg-plugin to sign artifacts.
Contributor
|
With this change, will future LTS release be done via release-please PRs instead of manually? |
mpeddada1
reviewed
Oct 27, 2025
Contributor
Author
Yes, that's right. The current release script (which does not create a release commit in the main branch or release branch) is not compatible with the new Kokoro infrastructure called Kokoro Instances. |
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.
This is part of b/452672128, where we want to stop using the old release cluster. The new infrastructure "Kokoro Instances" does not support release tag not on the main branch or release branches while the current release script in the
scriptfolder creates such release commits like that. To use the new cluster, we start to use Release Please thatThe bootstrap-sha points to
8eb8233. This is the parent commit of "Release 1.5.15-dependencies: Bumping to next version post release (#2408)".
LTS BOM 9.0.1 release happened after that.
New tag format is "-v". For example "gcp-lts-bom-v9.0.1" and "dependencies-v1.5.15". I'll need to change the release script and procedure to understand the tag format.
I experimented with my fork and created suztomo#5 via
~/release-please$ node ./build/src/bin/release-please.js release-pr --token=$GITHUB_TOKEN --repo-url=suztomo/cloud-opensource-java.