Spotless update#1221
Merged
Merged
Conversation
loosebazooka
force-pushed
the
spotless-update
branch
2 times, most recently
from
8909e36 to
97f91aa
Compare
Collaborator
|
I suggest automatic grouping like in pgjdbc/pgjdbc#4184 and apache/jmeter#6710 |
Need to add spotless at root to avoid shared build service issue Add renovate config to group updates Signed-off-by: Appu <appu@google.com>
loosebazooka
force-pushed
the
spotless-update
branch
from
97f91aa to
199102a
Compare
Member
Author
|
@vlsi does the automatic grouping pattern matching for renovate handle plugin matching? |
Collaborator
|
Renovate should group them automatically, and it does group when I execute renovate locally. |
Member
Author
|
okay rebased, should be ready for review |
vlsi
approved these changes
Jun 17, 2026
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.
Not sure if this is the most elegant solution, but seems to be what is required for this problem. We might be able to share version information via a toml version catalog. But hopefully updates happen as a group