Bump gradle-wrapper from 9.7.0 to 9.7.1 - #27
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 9.7.0 to 9.7.1. - [Release notes](https://github.com/gradle/gradle/releases) - [Commits](gradle/gradle@v9.7.0...v9.7.1) --- updated-dependencies: - dependency-name: gradle-wrapper dependency-version: 9.7.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
3 tasks
guyiome
added a commit
that referenced
this pull request
Sep 2, 2026
#29) (#31) * Bump the Gradle wrapper to 9.7.1 Reproduces Dependabot PR #27 as a local commit per project convention. Regenerated with ./gradlew wrapper --gradle-version 9.7.1 rather than hand-editing the properties file, so the wrapper jar is the one 9.7.1 actually ships instead of being left behind at 9.7.0. Verified the result is byte-identical to the PR: same blob hash for gradle-wrapper.jar, identical properties, and no other file touched (gradlew/gradlew.bat unchanged). 9.7.1 is a patch with six fixes. Only one is relevant here, and favourably: the regression in unit-test failure diff formatting. The others (ANTLR leaking into the kapt classpath, ant.taskdef classpath resolution, BaseExecSpec streams, Transformer implementations, Option argument ordering) cover mechanisms this project doesn't use. Full build, unit tests and lint pass on 9.7.1, and lint's "a newer version of Gradle is available" warning is now gone. * Bump com.android.application (AGP) to 9.3.2 Reproduces Dependabot PR #29 as a local commit per project convention; the resulting libs.versions.toml is identical to the PR's. Patch release, build/tests/lint all pass on it (on Gradle 9.7.1 from the previous commit, so the shipping combination is what got tested). Note: lint now reports AGP 9.4.0 as available too, released after this PR was opened. Deliberately not taken here -- a minor bump deserves its own changelog review rather than riding along in a patch reproduction, and Dependabot will raise it on its next run. * Bump actions/setup-java from v5 to v6 in all three workflows Reproduces Dependabot PR #28 as a local commit per project convention; the three resulting workflow files are identical to the PR's. Major version bump, but a no-op for how this repo uses the action (distribution: temurin, java-version: 17, nothing else). Reviewed the v6.0.0 notes against that usage: the Zulu Discovery -> Azul Metadata API migration only affects distribution: zulu; the jdkFile -> jdk-file rename concerns an input we don't set; the Maven/Gradle cache split concerns setup-java's own cache, which we don't use (caching goes through gradle/actions/setup-gradle); the GPG and Maven toolchain changes are unused here. The ESM migration is documented upstream as not user-facing. CI-only change, so it can't be validated locally -- the PR's own CI run is the check, and it was green on all three workflows. * Bump AGP further to 9.4.0, after reviewing the minor release Deliberate step beyond Dependabot PR #29 (reproduced as-is in the previous commit), taken only after checking the minor release rather than riding along with the patch. Requirements met: Gradle 9.6.0 minimum (we're on 9.7.1 as of two commits ago), JDK 17, SDK Build Tools 36.0.0 (installed). Neither announced behaviour change applies here: - Strict 1:1 flavor parity for dynamic features -- this project has a single app module and no dynamic features. - The new Variant API becoming mandatory in AGP 10 -- this project uses no Variant API at all (no applicationVariants, no androidComponents). The release APK is renamed by a plain mv in release.yml, not through the API, so there's nothing to migrate ahead of AGP 10 either. Validated with assembleRelease on top of the usual checks, because 9.4.0 carries a SigningConfig eagerness fix and this project relies on exactly that pattern (conditional release signingConfig falling back to signingConfigs.getByName("debug") when the env vars are absent). The fallback is intact: apksigner reports the release APK signed with "C=US, O=Android, CN=Android Debug" as before. Debug-only runs would not have caught a regression there. testDebugUnitTest, assembleDebug, lintDebug and assembleRelease all pass. Lint drops from 51 to 50 warnings -- the "newer version of AGP is available" one is now gone.
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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.
Bumps gradle-wrapper from 9.7.0 to 9.7.1.
Release notes
Sourced from gradle-wrapper's releases.
Commits
92f0512update fixed issues for 9.7.1 (#38892)820ee75update fixed issues for 9.7.182c23f9Fix annotation parameter ordering problem in KTS (#38878)ef11a72Fix annotation parameter ordering issuebb0d8a9Make relevant tests polyglot (run for multiple DSLs)336e129Update signing configuration (#38874)4bdf0daUpdate signing configurationcd9b92cList issues resolved in 9.7.1 (#38839)5f4e381List issues resolved in 9.7.11e08ab5Keep type-use annotations in extracted ABI classes (#38810)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)