chore(deps): update dependency gradle to v8

[renovate]

This PR contains the following updates:

Package	Update	Change
gradle (source)	major	7.6.2 -> 8.2.1

---

Release Notes

gradle/gradle (gradle)

v8.2.1: 8.2.1

Compare Source

This is a patch release for 8.2. We recommend using 8.2.1 instead of 8.2

It fixes the following issues:

• #​25579 Regression in 8.2: StackOverflowError w/ Gradle 8.2 + Quarkus 2.16.7 (latest)
• #​25611 TestKit unexpectedly stopped working with Gradle 2.x versions
• #​25618 Micronaut JacocoReportAggregationPlugin broken in Gradle 8.2
• #​25658 Gradle 8.2 sets incorrect value to boolean --no-feature option
• #​25674 Address regression in dependency graph build operation results

Read the Release Notes

Upgrade Instructions

Switch your build to use Gradle 8.2.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.2.1

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.2.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v8.2: 8.2

Compare Source

The Gradle team is excited to announce Gradle 8.2.

Amongst other improvements, this release addresses two security vulnerabilities:

• Dependency cache path traversal
• Path traversal vulnerabilities in handling of Tar archives

Read the Release Notes

We would like to thank the following community contributors for their contributions to this release of Gradle:

Bruno Didot,
Eric Vantillard,
esfomeado,
Jendrik Johannes,
Jonathan Leitschuh,
Lee Euije,
Stefan Oehme,
Todor Dinev,
Yanshun Li

Upgrade instructions

Switch your build to use Gradle 8.2 by updating your wrapper:

./gradlew wrapper --gradle-version=8.2

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.1.1: 8.1.1

Compare Source

This is a patch release for Gradle 8.1. We recommend using 8.1.1 instead of 8.1.

It fixes the following issues:

• #​24748 MethodTooLargeException when instrumenting a class with thousand of lambdas for configuration cache
• #​24754 Kotlin DSL precompiled script plugins built with Gradle 8.1 cannot be used with other versions of Gradle
• #​24788 Gradle 8.1 configure freeCompilerArgs for Kotlin in buildSrc breaks build with unhelpful errors

Read the Release Notes

Upgrade Instructions

Switch your build to use Gradle 8.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.1.1

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.1.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v8.1: 8.1

Compare Source

The Gradle team is excited to announce Gradle 8.1.

Read the Release Notes

We would like to thank the following community contributors for their contributions to this release of Gradle:

André Sousa,
Attila Király,
Aurimas,
Björn Kautler,
Christoph Dreis,
David Morris,
DJtheRedstoner,
Gabriel Feo,
J.T. McQuigg,
JavierSegoviaCordoba,
JayaKrishnan Nair K,
Jeff Widman,
kackey0-1,
Martin Bonnin,
Martin Kealey,
modmuss50,
pan93412,
Sebastian Schuberth,
Simon Marquis,
TheDadda,
Thrillpool,
valery1707,
Xin Wang,
Yanshun Li

Upgrade instructions

Switch your build to use Gradle 8.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.1

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.0.2: 8.0.2

Compare Source

The Gradle team is excited to announce Gradle 8.0.2.

This is the second patch release for Gradle 8.0. We recommend using 8.0.2 instead of 8.0.

It fixes the following issues:

• #​23698 Gradle 8 RC2 runs out of metaspace
• #​23962 Java/Scala build with no explicit toolchain: build fails with Gradle 8.0.1 / Scala 2.13
• #​23990 Gradle 8.0.+ silently dropped support for custom compilers in JavaCompile
• #​24031 InstrumentingTransformer generates different class files in Gradle 8 and 7.6 which leads to Remote Build-Cache misses
• #​24109 Extending an already resolved configuration no longer works correctly
• #​24122 Update configuration cache state for some plugins
• #​24129 includeBuild in PluginManagementSpec deincubated in Gradle 8, docs still say it's incubating

Issues fixed in the first patch release:

• #​21551 Document integration of Scala plugin with toolchains and problems with target flag
• #​23888 --no-rebuild suddenly gone without new deprecation cycle and without the reason for its undeprecation being void
• #​23905 Gradle 8.0 fails Scala build with isBlank not found in String class error

Read the Release Notes

Upgrade Instructions

Switch your build to use Gradle 8.0.2 by updating your wrapper:

./gradlew wrapper --gradle-version=8.0.2

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v8.0.1: 8.0.1

Compare Source

This is a patch release for 8.0. We recommend using 8.0.1 instead of 8.0.

It fixes the following issues:

• #​21551 - Document integration of Scala plugin with toolchains and problems with target flag
• #​23888 - --no-rebuild suddenly gone without new deprecation cycle and without the reason for its undeprecation being void
• #​23905 - Gradle 8.0 fails Scala build with isBlank not found in String class error

Read the Release Notes

Upgrade Instructions

Switch your build to use Gradle 8.0.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.0.1

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v8.0: 8.0

Compare Source

The Gradle team is excited to announce Gradle 8.0

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Abdul Rauf,
Andrei Nevedomskii,
aSemy,
Ben Cox,
Björn Kautler,
bodhili,
Cédric Champeau,
Christoph Dreis,
Clara Guerrero Sánchez,
David Marin Vaquero,
David Morris,
Denis Buzmakov,
Dmitry Pogrebnoy,
Dzmitry Neviadomski,
Eliezer Graber,
Eric Pederson,
Fedor Ihnatkevich,
Gabriel Rodriguez,
Herbert von Broeuschmeul,
Hyeonmin Park,
Jeff,
Jendrik Johannes,
Korov,
Marcono1234,
Madhead,
Mariell Hoversholm,
Matthew Haughton,
Matthias Ernst,
Michael Bailey,
Michael Ernst,
Michael Torres,
Pankaj,
prasad-333,
RicardoJiang,
Siddardha Bezawada,
Stephen Topley,
Victor Maldonado,
Vinay Potluri,
Xin Wang.

Upgrade instructions

Switch your build to use Gradle 8.0 by updating your wrapper:

./gradlew wrapper --gradle-version=8.0

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[ThrawnCA]

Build is unsuccessful, needs updates to be compatible with newer Gradle.

[ThrawnCA]

Build is broken.

[ThrawnCA]

Build is broken.

[hazendaz]

@JuditKnoll Seems Eclipse has similar issue, can you look at that one too?

[JuditKnoll]

@JuditKnoll Seems Eclipse has similar issue, can you look at that one too?

I tried to reproduce the build fail on my local machine, but couldn't. From the build failure log, created the #2479 PR, but there may be some other problems as well.

[hazendaz]

Hi @JuditKnoll so it continues to cascade, just apply all you think you need regardless if it makes build take longer or not. The builds are fast, not concerned on size, more concerned it actually works.

[hazendaz]

Anyone know what the docs failures actually mean? Suggests missing file but no file was removed and newer PRs are fine.

[JuditKnoll]

Anyone know what the docs failures actually mean? Suggests missing file but no file was removed and newer PRs are fine.

I have no idea, and I'm not even sure what triggers it. Reruning the build job didn't effect the Read the docs build.

Building the docs fails on my machine on both master and this branch for the same reason, but for a different one as in the github build.
If anyone has any info about this, it would be highly appreciated.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[JuditKnoll]

Rebased this PR via the rebase/retry checkbox thinking that's only a rebase, but it removed my already merged commits, so cherry-picked those. Now, all the checks are successful.
Thanks to @gtoison for looking into and solving the Read the docs build ( #2513 ).

[hazendaz]

@JuditKnoll The tic box for renovate will only do what you saw. Normally we probably wouldn't go to this extent against a bot branch but you figured it out and all good now, merged in, thanks.