ci: dependencies as a module in Release Please in master branch #2448
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
mpeddada1
approved these changes
Oct 29, 2025
Contributor
Author
|
I'll fix the Gradle build failure in subsequent pull request. |
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 change splits the dependencies module as an independent module rather than using the root. When we used the root "." as the Release Please's module, then it mixes up LTS changes with dependencies module. See #2447 having "LTS 9" as a minor version bump to the dependencies module release.
This change also updates the Gradle plugin's version declaration from the gradle.properties to build.gradle with Release Please annotation. Release Please annotation is easier in build.gradle as it supports
//with source code comment.