ktorio / ktor-build-plugins

Ktor Plugins for Build Systems
Apache License 2.0
56 stars 10 forks source link

Update dependency gradle to v8 #75

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Update Change
gradle (source) major 7.6 -> 8.0.2

Release Notes

gradle/gradle ### [`v8.0.2`](https://togithub.com/gradle/gradle/releases/tag/v8.0.2): 8.0.2 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](https://togithub.com/gradle/gradle/issues/23698) Gradle 8 RC2 runs out of metaspace - [#​23962](https://togithub.com/gradle/gradle/issues/23962) Java/Scala build with no explicit toolchain: build fails with Gradle 8.0.1 / Scala 2.13 - [#​23990](https://togithub.com/gradle/gradle/issues/23990) Gradle 8.0.+ silently dropped support for custom compilers in `JavaCompile` - [#​24031](https://togithub.com/gradle/gradle/issues/24031) InstrumentingTransformer generates different class files in Gradle 8 and 7.6 which leads to Remote Build-Cache misses - [#​24109](https://togithub.com/gradle/gradle/issues/24109) Extending an already resolved configuration no longer works correctly - [#​24122](https://togithub.com/gradle/gradle/issues/24122) Update configuration cache state for some plugins - [#​24129](https://togithub.com/gradle/gradle/issues/24129) includeBuild in PluginManagementSpec deincubated in Gradle 8, docs still say it's incubating Issues fixed in the first patch release: - [#​21551](https://togithub.com/gradle/gradle/issues/21551) Document integration of Scala plugin with toolchains and problems with `target` flag - [#​23888](https://togithub.com/gradle/gradle/issues/23888) `--no-rebuild` suddenly gone without new deprecation cycle and without the reason for its undeprecation being void - [#​23905](https://togithub.com/gradle/gradle/issues/23905) Gradle 8.0 fails Scala build with isBlank not found in String class error [Read the Release Notes](https://docs.gradle.org/8.0.2/release-notes.html) #### 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](https://docs.gradle.org/8.0.2/userguide/upgrading_version\_7.html#changes\_8.0) 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](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v8.0.1`](https://togithub.com/gradle/gradle/releases/tag/v8.0.1): 8.0.1 This is a patch release for 8.0. We recommend using 8.0.1 instead of 8.0. It fixes the following issues: - [#​21551](https://togithub.com/gradle/gradle/issues/21551) - Document integration of Scala plugin with toolchains and problems with `target` flag - [#​23888](https://togithub.com/gradle/gradle/issues/23888) - `--no-rebuild` suddenly gone without new deprecation cycle and without the reason for its undeprecation being void - [#​23905](https://togithub.com/gradle/gradle/issues/23905) - Gradle 8.0 fails Scala build with isBlank not found in String class error [Read the Release Notes](https://docs.gradle.org/8.0.1/release-notes.html) #### 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](https://docs.gradle.org/8.0.1/userguide/upgrading_version\_7.html#changes\_8.0) 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](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v7.6.1`](https://togithub.com/gradle/gradle/releases/tag/v7.6.1): 7.6.1 This is a patch release for 7.6. We recommend using 7.6.1 instead of 7.6. It fixes the following issues: - [#​19065](https://togithub.com/gradle/gradle/issues/19065) Platform dependencies not possible in dependency block of test suite plugin - [#​22688](https://togithub.com/gradle/gradle/issues/22688) Increased memory usage (with -p option) - [#​22796](https://togithub.com/gradle/gradle/issues/22796) Building gradle itself fails during toolchain download: permission denied copying a file within `.gradle/jdks` - [#​22875](https://togithub.com/gradle/gradle/issues/22875) Regression with 7.6: @​​pom artifact in JVM library project is no longer found - [#​22937](https://togithub.com/gradle/gradle/issues/22937) Remove safe credentials reference - [#​22973](https://togithub.com/gradle/gradle/issues/22973) Kotlin MPP plugin broken with Gradle 7.6 due to signature change in TestResultProcessor - [#​23016](https://togithub.com/gradle/gradle/issues/23016) toolchainManagement.jvm.javaRepositories should not expose the full surface of NamedDomainObjectList - [#​23025](https://togithub.com/gradle/gradle/issues/23025) Back-port toolchain related fixes to 7.6.1 - [#​23053](https://togithub.com/gradle/gradle/issues/23053) Auto-provisioning/auto-detection of IBM Semeru toolchains is broken with Gradle 7.6 - [#​23074](https://togithub.com/gradle/gradle/issues/23074) Docs: Build Lifecycle starts halfway through a point - [#​23096](https://togithub.com/gradle/gradle/issues/23096) Classifiers of version catalog are discarded while copied to anothor dependency - [#​23111](https://togithub.com/gradle/gradle/issues/23111) Ant closures are broken with Gradle 7.6 - [#​23178](https://togithub.com/gradle/gradle/issues/23178) Mention the Foojay Toolchain Resolver plugin in the Gradle manual - [#​23215](https://togithub.com/gradle/gradle/issues/23215) Gradle 7.6: high memory usage (android project) - [#​23224](https://togithub.com/gradle/gradle/issues/23224) Backport to 7.6.1 "Fix for Incremental compilation with modules" - [#​23294](https://togithub.com/gradle/gradle/issues/23294) "Unable to make progress running work" together with --continue and failing tasks (Backport to 7.6.1) - [#​23555](https://togithub.com/gradle/gradle/issues/23555) Improve Toolchain related deprecation nagging in 7.6 - [#​23894](https://togithub.com/gradle/gradle/issues/23894) Update EOL policy - [#​23910](https://togithub.com/gradle/gradle/issues/23910) Backport trusting only full GPG keys in dependency verification \[Backport 7.6.1] - [#​23941](https://togithub.com/gradle/gradle/issues/23941) Typo in v7.6 docs about disabling_the_daemon - [#​23985](https://togithub.com/gradle/gradle/issues/23985) Resolving of manually created configuration creates a ResolveException [Read the Release Notes](https://docs.gradle.org/7.6.1/release-notes.html) #### Upgrade Instructions Switch your build to use Gradle 7.6.1 by updating your wrapper: ./gradlew wrapper --gradle-version=7.6.1 See the [Gradle 7.x upgrade guide](https://docs.gradle.org/7.6.1/userguide/upgrading_version\_7.html#changes\_7.6) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.6.1. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss).

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.



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

e5l commented 1 year ago

@maratdin7, could you take a look?

renovate[bot] commented 1 year ago

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.