Record verified upstream status in the Gradle 9.6 deprecations tracker#732
Merged
Conversation
Re-verify the third-party deprecation warnings on Gradle 9.6.1 with full
deprecation stack traces (`-Dorg.gradle.deprecation.trace=true`) and
record the findings in `.agents/tasks/gradle-9.6-deprecations.md`:
- detekt 1.23.8 - `ReportingExtension.file(String)` raised by
`DetektPlugin.apply`. The upstream fix (detekt#8452, closed 2025-08-31)
ships only with detekt 2.0, still in alphas, under the new `dev.detekt`
plugin ID and Maven coordinates. 1.23.8 remains the newest stable.
- gradle-doctor 0.12.1 - `Project.getProperties` is read three times by
`RemoteCacheEstimation` (lines 20-22). Unfixed even on upstream
`master`; no upstream issue tracks it; 0.12.1 has no git tag, so watch
Maven Central metadata instead of GitHub releases.
- Kover 0.9.8 - add the third, cache-masked warning ("Project object as
a dependency notation", `PrepareKover.kt:29`, kotlinx-kover#818). It
fires during `buildSrc` precompiled-script-plugin accessor generation
and is hidden when those tasks are FROM-CACHE. This is the follow-up
suggested when closing PR #725, and is distinct from the
`KoverConfig.kt` usage handled separately.
No plugin bumps are possible: all three plugins are already at their
latest released versions. The tracker stays `blocked` on upstream.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6a8316388e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
armiol
approved these changes
Jul 10, 2026
Review follow-up on PR #732: the tracker could previously be closed once the three plugin-internal warnings clear, silently leaving behind the same Gradle 10 breakage in config-owned code - KoverConfig.kt:172 passes a `Project` as dependency notation, which only fires in consumer builds whose subprojects apply Kover and thus never shows in config's own runs. Track that call as an explicit checklist item (it is fixed in a separate change that has not landed on master yet) and require a warning-free cold-cache run of both reproduce commands before the tracker may be closed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What & why
Follow-up to #719's deprecation cleanup: attribute the deprecation warnings still reported by
./gradlew :buildSrc:test detekt --warning-mode allto their sources using full deprecation stack traces (-Dorg.gradle.deprecation.trace=true), and record the verified findings in the standing tracker.agents/tasks/gradle-9.6-deprecations.md.No build-logic changes — all remaining warnings originate inside third-party plugins, and none of them has a fixed release to bump to. All three become hard errors in Gradle 10.
ReportingExtension.file(String)DetektPlugin.kt:28)dev.detektplugin ID and coordinates) — detekt#8452, closed 2025-08-31Project.getProperties(×3)RemoteCacheEstimation.kt:20–22)master; no upstream issue; 0.12.1 is tagless — watch Maven Central metadataProjectobject as a dependency notationPrepareKover.kt:29)Tracker changes
dev.detektplugin-ID/coordinate migration caveat for the future bump (not a plain version bump).buildSrcgenerates precompiled-script-plugin accessors and is invisible when those tasks areFROM-CACHE. Reproduce with:./gradlew :buildSrc:generatePrecompiledScriptPluginAccessors --rerun-tasks \ --warning-mode all -Dorg.gradle.deprecation.trace=trueconfig's ownProject-notation usage inKoverConfig.kt:172, which is addressed separately — fixingKoverConfigdoes not clear the plugin-internal warning.blocked(on upstream releases).Reviewer notes
./gradlew :buildSrc:test detekt --warning-mode all --stacktraceis green, and the cold accessor-generation run above reproduces the Kover warning with the quoted stack frame (kotlinx.kover.gradle.plugin.appliers.PrepareKoverKt.prepare).🤖 Generated with Claude Code