build(deps): bump org.jlleitschuh.gradle:ktlint-gradle from 11.1.0 to 14.2.0#4867
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
added
Dependencies
dependabot
Bot
force-pushed
the
dependabot/gradle/org.jlleitschuh.gradle-ktlint-gradle-14.2.0
branch
from
ab342cd to
239c07c
Compare
Bumps org.jlleitschuh.gradle:ktlint-gradle from 11.1.0 to 14.2.0. --- updated-dependencies: - dependency-name: org.jlleitschuh.gradle:ktlint-gradle dependency-version: 14.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/gradle/org.jlleitschuh.gradle-ktlint-gradle-14.2.0
branch
from
239c07c to
6732899
Compare
DeepDiver1975
left a comment
DeepDiver1975
left a comment
Member
There was a problem hiding this comment.
Build-tooling dependency bump: org.jlleitschuh.gradle:ktlint-gradle 11.1.0 → 14.2.0 (a three-major-version jump). Single-line change in gradle/libs.versions.toml.
What's verified by CI here:
- All required checks are green (
assembleDebug, unit + instrumented data tests, Detekt, validations). Because the ktlint-gradle plugin is applied to all subprojects inbuild.gradle, a greenassembleDebugconfirms the new plugin version applies cleanly with the project's current Gradle/JDK — that's the main build-breaking risk (ktlint-gradle 12+ raised its minimum Gradle/JDK requirements) and it's covered. 👍
What's NOT verified by CI:
- No workflow runs a
ktlintCheck/ktlintFormattask — onlydetektruns as a lint gate. A jump from the ktlint engine bundled in 11.x to the one in 14.x adds/changes rules, so any new formatting violations are not surfaced by these checks. They would only appear for developers who run ktlint locally (or in IDE), and they will not break the build.
Assessment: build-tooling/dev dependency, no production code affected; changelog n/a. The build-compat risk is covered by green CI, so this is reasonable to merge. Flagging — not blocking — that the new ktlint ruleset isn't exercised in CI, so consider a quick local ./gradlew ktlintCheck (or adding it to CI) before/after merge to catch any new rule violations. Leaving the merge call to a maintainer.
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.
Bumps org.jlleitschuh.gradle:ktlint-gradle from 11.1.0 to 14.2.0.