Bump gradle-wrapper from 8.11 to 9.5.0#343
Conversation
Bumps [gradle-wrapper](https://github.com/gradle/gradle) from 8.11 to 9.5.0. - [Release notes](https://github.com/gradle/gradle/releases) - [Commits](gradle/gradle@v8.11.0...v9.5.0) --- updated-dependencies: - dependency-name: gradle-wrapper dependency-version: 9.5.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
|
Gradle9 sees some in-use methods being removed. Moving to Gradle9 build would require either invoking methods via reflect (ugly) or dropping support for some older versions of Gradle, specifically, it looks like the oldest Gradle the plugin would support would change from 5.1 to 7.1. This would be a breaking change, requiring a major version bump. It's worth noting that the 2.0.0 release was supposed to move the plugin to requiring Java 17, but that doesn't seem to be the case. Target Java version is still 11. Many libraries are moving to having Java 17 as a minimum and being on Java 11 is already starting to mean some dependency can't, or are a pain, to update. A 3.0.0 release could move to Java 17 and a Gradle 9 build, with oldest supported Gradle version of 7.1 I'd appreciate thoughts from the community on this. |
1 participant
Bumps gradle-wrapper from 8.11 to 9.5.0.
Release notes
Sourced from gradle-wrapper's releases.
... (truncated)
Commits
3fe117dUpdate jdks.yaml (#37703)33d145aUpdate jdks.yamlf7a05d1Update Gradle wrapper to version 9.5.0-rc-4 (#37654)266facdUpdate Gradle wrapper to version 9.5.0-rc-40ad6dd8Suppress OSC taskbar reset on plain/piped stdout (#37646)966025dSuppress OSC taskbar reset on plain/piped stdoute745573Polish IP docs (#37642)d5cfd07Ensure BuildOperationQueue will progress without extra leases (#37629)acdf0c3Ensure BuildOperationQueue will progress without extra leasesf7d0e4fRename anchorDependabot 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)