This repository was archived by the owner on May 24, 2023. It is now read-only.
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.
This PR contains the following updates:
v2
->v3
v2
->v3
v1
->v3
v2
->v4
v1
->v2
v1
->v2
v1
->v2
v1
->v2
7.4
->8.0.2
4.1.1
->5.0.0
Release Notes
actions/checkout
v3
Compare Source
actions/setup-java
v3
Compare Source
docker/build-push-action
v4
Compare Source
v3
Compare Source
docker/login-action
v2
Compare Source
docker/setup-buildx-action
v2
Compare Source
docker/setup-qemu-action
v2
Compare Source
github/codeql-action
v2
Compare Source
gradle/gradle
v8.0.2
: 8.0.2The 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:
JavaCompile
Issues fixed in the first patch release:
target
flag--no-rebuild
suddenly gone without new deprecation cycle and without the reason for its undeprecation being voidRead the Release Notes
Upgrade Instructions
Switch your build to use Gradle 8.0.2 by updating your wrapper:
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.1This is a patch release for 8.0. We recommend using 8.0.1 instead of 8.0.
It fixes the following issues:
target
flag--no-rebuild
suddenly gone without new deprecation cycle and without the reason for its undeprecation being voidRead the Release Notes
Upgrade Instructions
Switch your build to use Gradle 8.0.1 by updating your wrapper:
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.
v7.6.1
: 7.6.1This is a patch release for 7.6. We recommend using 7.6.1 instead of 7.6.
It fixes the following issues:
.gradle/jdks
Read the Release Notes
Upgrade Instructions
Switch your build to use Gradle 7.6.1 by updating your wrapper:
See the Gradle 7.x upgrade guide 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
v7.5.1
: 7.5.1This is a patch release for 7.5. We recommend using 7.5.1 instead of 7.5
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Michael Bailey,
Josh Kasten,
Marcono1234,
mataha,
Lieven Vaneeckhaute,
kiwi-oss,
Stefan Neuhaus,
George Thomas,
Anja Papatola,
Björn Kautler,
David Burström,
Vladimir Sitnikov,
Roland Weisleder,
Konstantin Gribov,
David Op de Beeck,
aSemy,
Rene Groeschke,
Jonathan Leitschuh,
Aurimas Liutikas,
Jamie Tanna,
Xin Wang,
Atsuto Yamashita,
Taeik Lim,
Peter Gafert,
Alex Landau,
Jerry Wiltse,
Tyler Burke,
Matthew Haughton,
Filip Daca,
Simão Gomes Viana,
Vaidotas Valuckas,
Edgars Jasmans,
Tomasz Godzik,
Jeff,
Lajos Veres
Upgrade instructions
Switch your build to use Gradle 7.5.1 by updating your wrapper:
./gradlew wrapper --gradle-version=7.5.1
See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
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.
v7.4.2
: 7.4.2This is a patch release for Gradle 7.4.
See the list of fixed issues: https://docs.gradle.org/7.4.2/release-notes.html
We recommend users upgrade to 7.4.2 instead of 7.4 or another patch release.
Upgrade Instructions
Switch your build to use Gradle 7.4.2 by updating your wrapper:
See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.4.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.
v7.4.1
: 7.4.1This is a patch release for Gradle 7.4.
See the list of fixed issues: https://docs.gradle.org/7.4.1/release-notes.html
We recommend users upgrade to 7.4.1 instead of 7.4.
Upgrade Instructions
Switch your build to use Gradle 7.4.1 by updating your wrapper:
See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.4.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.
ajoberstar/grgit
v5.0.0
Compare Source
This release includes a number of breaking changes, with the main user highlight being the long awaited configuration cache support.
Known Issue: #356 highlighted that (some?) multi-project builds will encounter an error when applying
org.ajoberstar.grgit
ororg.ajoberstar.grgit.service
to multiple projects. This is caused by an upstream Gradle issue https://github.com/gradle/gradle/issues/17559 that is, as of 2/10/2022, is targeted to be fixed in 7.5. I suggest multi-project builds hold off on upgrading until that upstream issue is resolved.Breaking Changes
org.ajoberstar.grgit
is no longer auto-applied to all subprojects, you must apply it to any project that wants to access thegrgit
propertyEnhancements
--configuration-cache
is now supported (thanks @abelom and @runningcode)org.ajoberstar.grgit-service
plugin is available to provide lazy access to aGrgitService
(a Gradle BuildService). See the README for tips on how to use this.grgit.remote.remove(name: 'origin')
to remove remotesFixes
None
Deprecations
None
Compatibility
Tested on the following version:
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.