Repository navigation
build(deps): update Spotless to 8.10.3 - #2207
Merged
Bambooin merged 1 commit intoOct 29, 2026
Merged
Conversation
X2M7
marked this pull request as ready for review
October 29, 2026 05:48
Bambooin
approved these changes
Oct 29, 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
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.
Update Spotless from 8.10.2 to 8.10.3 to avoid the deprecated
Configuration.setVisible(false)call on Gradle 9+. This includes the dependency fix for diffplug/spotless#3099. The plugin ID, target patterns, and explicitly pinned ktlint 1.8.0 stay unchanged.Local A/B runs executed both formatter and check actions with Gradle 9.8.1 and deprecation tracing. The Spotless-origin warning traces to
GradleProvisionerin the baseline and disappears after the upgrade. Both runs checked the same 293 tracked Kotlin files with identical paths and contents.The 52 Android Gradle Plugin and three KSP calls producing the same deprecation remain, so Gradle can still print
setVisiblewarnings. The three separate included-build output warnings also remain; #2206 addresses those. This change does not claim that all project warnings are gone.All five upstream CI checks passed. Source-bound validation and retained diagnostics record the actual tasks and distinguish native compilation from cache reuse. No device or release validation is claimed for this build-tool update.