Conversation
jbonofre
requested review from
kou,
laurentgo,
lidavidm and
wgtmac
as code owners
October 5, 2026 14:37
Member
|
We may not need this because you already used |
jbonofre
force-pushed
the
dependabot-ignore-checkstyle-13
branch
from
October 6, 2026 05:23
79191e8 to
c9ed3df
Compare
Member
Author
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
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.
Rationale for this change
Dependabot PR #1324 bumps Checkstyle from 10.23.0 to 14.3.0 and fails on every JDK 17 job with:
Checkstyle 13.0.0 and later are built for Java 21, while the build still runs on JDK 17. The 12.x line is the last one built for Java 17.
What changes are included in this PR?
Add an
ignorerule to the Maven ecosystem in.github/dependabot.ymlso Dependabot no longer proposes Checkstyle>=13. Updates within 12.x are still proposed.Are these changes tested?
No, this is a CI configuration change only. The YAML was checked to parse.
Are there any user-facing changes?
No.