New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update all #7
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update all #7
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
August 17, 2022 03:02
46e8d8c
to
3aa69c8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
August 19, 2022 03:54
3aa69c8
to
ed5aabd
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
August 26, 2022 17:23
ed5aabd
to
ec4bb35
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
September 10, 2022 22:03
9a00168
to
90f43da
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
September 21, 2022 18:01
75c01da
to
166546b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
October 3, 2022 19:45
8e37b31
to
300543f
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
October 14, 2022 00:49
76cae77
to
6251456
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
October 25, 2022 15:21
440fe09
to
a7fa14f
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
November 3, 2022 23:57
ab43cd5
to
f9e1dcb
Compare
renovate
bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
November 14, 2022 04:30
f880cec
to
3f8997c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
December 25, 2023 09:28
440aba1
to
9e6b9a6
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 3, 2024 18:35
9e6b9a6
to
09b9492
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
January 10, 2024 19:35
09b9492
to
4a16fed
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
January 25, 2024 01:18
835288f
to
e170977
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
February 7, 2024 19:42
8007e1d
to
9306491
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
February 24, 2024 02:05
7fd0860
to
ec7bf18
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
March 6, 2024 20:42
3e4eaa0
to
0bca8db
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
March 8, 2024 00:37
0bca8db
to
a1a806a
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
March 22, 2024 16:25
68c14fc
to
84f19b5
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
April 10, 2024 05:47
65eb740
to
0d5fb0e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
April 17, 2024 20:27
33ee628
to
39b2045
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
May 2, 2024 22:27
b3066e5
to
f573026
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
May 14, 2024 19:42
1f59881
to
8c36262
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
May 20, 2024 23:49
8c36262
to
64a3ff4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
8.0
->8.7
v2.6.0
->v2.12.0
3.5.0
->3.5.1
1.1.4
->1.1.5
0.27.0
->0.34.0
0.27.0
->0.34.0
0.27.0
->0.34.0
2.2.2
->2.6.0
2.7.4
->2.7.7
1.1.0-alpha02
->1.2.1
2.6.0-alpha03
->2.8.0
1.6.1
->1.9.0
1.2.0-alpha02
->1.2.0-alpha04
2.5.1
->2.8.0
2.5.1
->2.8.0
2.5.1
->2.8.0
1.2.0
->1.2.1
4.13.2
->4.16.0
1.9.0
->1.13.1
0.3.5
->0.3.7
1.5.3
->1.5.14
3.4.0
->3.5.1
1.1.3
->1.1.5
1.1.1
->1.2.4
2.2.0
->2.3.0
1.6.1
->1.12.0
1.5.0
->1.6.1
1.8.0
->1.13.1
8.0.2
->8.4.1
8.0.2
->8.4.1
8.0.2
->8.4.1
1.9.10-1.0.13
->1.9.24-1.0.20
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
gradle/gradle (gradle)
v8.7
Compare Source
v8.6
Compare Source
v8.5
: 8.5Compare Source
The Gradle team is excited to announce Gradle 8.5.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Ahmed Ehab,
Alex Landau,
Aurimas,
Björn Kautler,
bodhili,
Daniel Le Berre,
davidburstrom,
Franz Wimmer,
Jongwoo Han,
Ken,
Leonardo Silveira,
Martin Bonnin,
Matthew Von-Maszewski,
Nik Clayton,
noeppi_noeppi,
Philip Wedemann,
Philipp Schneider,
Tomas Bjerre
Upgrade instructions
Switch your build to use Gradle 8.5 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
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.
v8.4
: 8.4Compare Source
The Gradle team is excited to announce Gradle 8.4.
Amongst other improvements, this release addresses two security vulnerabilities:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Ahmed Ehab,
Andrei Rybak,
Baptiste Decroix,
Björn Kautler,
Cesar de la Vega,
Ganavi Jayaram,
Gaurav Padam,
hwanseok,
J.T. McQuigg,
Jakub Chrzanowski,
Jendrik Johannes,
kackey0-1,
Konstantin Gribov,
Pratik Haldankar,
Qinglin,
Sebastian Schuberth,
Thad House,
valery1707,
Vladimir Sitnikov,
wuyangnju,
Yanming Zhou,
Yanshun Li,
Yusuke Uehara,
zeners
Upgrade instructions
Switch your build to use Gradle 8.4 by updating your wrapper:
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.3
: 8.3Compare Source
The Gradle team is excited to announce Gradle 8.3.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Ahmed Ehab,
Aurimas,
Baptiste Decroix,
Björn Kautler,
Borewit,
Korov,
Mohammed Thavaf,
Patrick Brückner,
Philip Wedemann,
Róbert Papp,
Shi Chen,
Tony Robalik
Upgrade instructions
Switch your build to use Gradle 8.3 by updating your wrapper:
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.2.1
Compare Source
v8.2
: 8.2Compare Source
The Gradle team is excited to announce Gradle 8.2.
Amongst other improvements, this release addresses two security vulnerabilities:
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.1Compare 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:
Read the Release Notes
Upgrade Instructions
Switch your build to use Gradle 8.1.1 by updating your wrapper:
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.1Compare 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.2Compare 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:
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.1Compare Source
This 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.
gradle/gradle-build-action (gradle/gradle-build-action)
v2.12.0
Compare Source
Adds a new option to clear a previously submitted dependency-graph.
This may prove useful when migrating to a workflow using the upcoming
gradle/actions/dependency-submission
action.Full-changelog: gradle/gradle-build-action@v2.11.1...v2.12.0
v2.11.1
Compare Source
This patch release fixes an issue that prevented the
gradle-build-action
from executing with Gradle 1.12, and improves error reporting for dependency submission failures.Changelog
Full-changelog: gradle/gradle-build-action@v2.11.0...v2.11.1
v2.11.0
Compare Source
In addition to a number of dependency updates, this release:
Changelog
Full-changelog: gradle/gradle-build-action@v2.10.0...v2.11.0
v2.10.0
Compare Source
This release introduces a new
artifact-retention-days
parameter, which allows a user to configure how long the generated dependency-graph artifacts are retained by GitHub Actions. Adjusting the retention period can be useful to reduce storage costs associated with these dependency-graph artifacts.See the documentation for more details.
Changelog
artifact-retention-days
configuration parameter #903v1.0.0
of the github-dependency-graph-gradle-plugin@babel/traverse
to address reported security vulnerabilityFull-changelog: gradle/gradle-build-action@v2.9.0...v2.10.0
v2.9.0
Compare Source
The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the
dependency-review-action
.See the documentation for detailed examples.
Changelog
pull-request
events #882dependency-review-action
#879Full-changelog: gradle/gradle-build-action@v2.8.1...v2.9.0
v2.8.1
Compare Source
Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.
Fixes
Changelog
v2.8.0
Compare Source
The
v2.8.0
release of thegradle-build-action
introduces an easy mechanism to connect to Gradle Enterprise, as well improved support for self-hosted GitHub Actions runners.Automatic injection of Gradle Enterprise connectivity
It is now possible to connect a Gradle build to Gradle Enterprise without changing any of the Gradle project sources. This is achieved through Gradle Enterprise injection, where an init-script will apply the Gradle Enterprise plugin and associated configuration.
This feature can be useful to easily trial Gradle Enterprise on a project, or to centralize Gradle Enterprise configuration for all GitHub Actions workflows in an organization.
See Gradle Enterprise injection in the README for more info.
Restore Gradle User Home when directory already exists
Previously, the Gradle User Home would not be restored if the directory already exists. This wasn't normally an issue with GitHub-hosted runners, but limited the usefulness of the action for persistent, self-hosted runners.
This behaviour has been improved in this release:
Changes
Issues fixed: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed
Full changelog: gradle/gradle-build-action@v2.7.1...v2.8.0
v2.7.1
Compare Source
This release contains no code changes, only dependency updates and documentation improvements.
Changelog
v2.7.0
Compare Source
GitHub Dependency Graph support
In this release, the GitHub Dependency Graph support is no longer considered "experimental", and should be considered ready for production use. You can read more about the Dependency Graph support in the README chapter.
Changes
github-dependency-graph-gradle-plugin@v0.2.0
dependency-graph-file
output to any step that generates a Dependency Graph fileChangelog
v2.6.1
Compare Source
Dependency Graph support
This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support:
job.correlator
value for each Gradle invocation within a Job. This permits multiple Gradle invocations in a single job to generate and submit a separate dependency graph.github-dependency-graph-gradle-plugin@v0.1.0
, which brings a number of improvements to the generated dependency graph:google/accompanist (com.google.accompanist:accompanist-drawablepainter)
v0.34.0
: 🌈What’s Changed
v0.32.0
: 🌈What’s Changed
v0.30.1
: 🌈What’s Changed
v0.30.0
: 🌈What’s Changed
v0.28.0
: 🌈What’s Changed
v0.27.1
: 🌈What’s Changed
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.
👻 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.