Remove deprecated Configuration.isVisible usages - #3237
Merged
Merged
Conversation
troelsbjerre
approved these changes
Oct 2, 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.
Gradle 9.8.0 deprecated Configuration.setVisible(boolean), scheduled for
removal in Gradle 11, causing deprecation warnings whenever the KSP
Gradle plugin is applied. The property has had no effect since Gradle 9.0
Before that, it only
caused
assembleto build a configuration's artifacts. All affected KSPconfigurations are non-consumable and have no outgoing artifacts, so
removing the calls changes nothing on older Gradle versions either.