Make the Gradle-version CI matrix use the requested Gradle version

[mernst]

The test-gradle job passes -Ptest.gradle-version but no test.java-toolchain, and build.gradle.kts forwarded the Gradle version to the test JVM only when the toolchain property was also set. Every matrix job therefore ran against the Gradle version embedded in the build.

Forwarding the property reveals that Gradle below 8.2.1 cannot configure a Kotlin DSL build script that applies this plugin, because the plugin is compiled by the Kotlin compiler embedded in a newer Gradle. Skip the Kotlin DSL tests there; the Groovy tests still cover those Gradle versions.

Also refresh the version matrix and fix the test-report artifact path, which named a source set that does not exist.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Gradle compatibility matrix now includes newer patch releases and documents the Kotlin DSL limitation below Gradle 8.2.1. The Gradle version property is configured independently from the Java toolchain property. Functional test reports use the functional test report directory. Kotlin DSL functional tests define Gradle 8.2.1 as the minimum supported version and skip setup for older versions.

Possibly related PRs

• typetools/checker-framework-gradle-plugin#16: Shares the functional-test infrastructure updated by this change.
• typetools/checker-framework-gradle-plugin#25: Shares Gradle configuration, compatibility matrix, and Kotlin functional-test changes.
• typetools/checker-framework-gradle-plugin#27: Also updates the Gradle compatibility test matrix.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch config-cache-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/gradle.yml:
- Around line 61-65: Add a job-level permissions block to the test-gradle job,
granting only contents: read for its checkout, setup, Gradle, and
artifact-upload steps; leave all other token scopes omitted.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c885008a-17c0-4d9f-9f29-9d499abd23d5

📥 Commits

Reviewing files that changed from the base of the PR and between de659cf and 6fb5897.

📒 Files selected for processing (4)

• .github/workflows/gradle.yml
• build.gradle.kts
• src/functionalTest/kotlin/org/checkerframework/plugin/gradle/Fixtures.kt
• src/functionalTest/kotlin/org/checkerframework/plugin/gradle/KotlinPluginFunctionalTest.kt