Update all dependencies - autoclosed #199
Closed
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
7566127 to
e54cc27
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
e54cc27 to
164d686
Compare
renovate
bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
0459584 to
db2914c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
e8ba1bd to
d5f6cc2
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
d5f6cc2 to
6f9bc67
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
92822ea to
79da2bc
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
f076cd3 to
b74d0cd
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
b74d0cd to
d8ad7fe
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
d8ad7fe to
ca00b77
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
ca00b77 to
57d3566
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
c0eefd3 to
7a4243b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
7a4243b to
73fb608
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
d0534e3 to
c678a68
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
bc4dac2 to
302d1b9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
302d1b9 to
2041fee
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1->8.45.9.2->5.10.04.10.0->4.11.05.0.0-beta.6->5.0.0-beta.155.2.0->5.6.04.13.0->4.14.05.9.2->5.10.05.9.2->5.10.01.3.1->1.3.61.36->1.374.13.0->4.14.04.3.0->4.3.11.19-R0.1-SNAPSHOT->1.20-R0.15.9.2->5.10.05.9.2->5.10.01.3.1->2.1.05.2.0->5.6.0Release Notes
gradle/gradle (gradle)
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.1Compare 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.2Reporting 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.1Reporting 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:
JavaCompileIssues fixed in the first patch release:
targetflag--no-rebuildsuddenly 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.
mockito/mockito (org.mockito:mockito-core)
v5.6.0Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optionalis notemptywhen usingRETURN_DEEP_STUBS(#2865)v5.5.0Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0Changelog generated by Shipkit Changelog Gradle Plugin
5.4.0
@Mock(serializable = true)for parameterized types. (#3007)ArgumentMatchers#any()JavaDoc(#3003)
@Mock(serializable = true)no longer works with parameterized types (#2979)v5.3.1Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotationsparameter to@Mock(#2965)ArgumentMatchers#assertArgmethod. (#2949)KyoriPowered/adventure (net.kyori:adventure-text-serializer-legacy)
v4.14.0: 🌏 Adventure 4.14.0Adventure 4.14.0 is a feature release introducing some long-awaited API additions, primarily focused on component serializers.
✨ Features
🔧 Changes
As a small programming note, the changes necessary to introduce the
text-serializer-jsonabstraction have shifted things around in the Adventure module dependency graph.adventure-text-serializer-gsonnow depends onadventure-text-serializer-json. Additionally,adventure-text-serializer-gson-legacyimplnow depends onadventure-text-serializer-json-legacyimpl, and is entirely deprecated, to be replaced with thejsonversion. In 4.15.0, we will no longer ship the deprecated submodule -- any users who need it can continue to depend on the older version. To facilitate this change,adventure-text-serializer-gson-legacyimplhas been removed from the bom to avoid improperly forcing version alignment.🐛 Fixes
New Contributors
Full Changelog: KyoriPowered/adventure@v4.13.1...v4.14.0
v4.13.1: 🌏 Adventure 4.13.1Adventure 4.13.1 is a bugfix release with fixes focused around MiniMessage and translatable component fallbacks. We recommend updating at your earliest convenience.
Fixes 🐛
New Contributors
Full Changelog: KyoriPowered/adventure@v4.13.0...v4.13.1
dzikoysk/expressible (org.panda-lang:expressible)
v1.3.5Compare Source
What's Changed
Full Changelog: dzikoysk/expressible@1.3.4...1.3.5
v1.3.4What's Changed
Full Changelog: dzikoysk/expressible@1.3.0...1.3.4
openjdk/jmh (org.openjdk.jmh:jmh-generator-annprocess)
v1.37Compare Source
KyoriPowered/adventure-platform (net.kyori:adventure-platform-api)
v4.3.1This is a bugfix release to add support for Minecraft 1.20.2 on the Bukkit platform.
What's Changed
New Contributors
Full Changelog: KyoriPowered/adventure-platform@v4.3.0...v4.3.1
KyoriPowered/blossom (net.kyori:blossom)
v2.1.0: 🌼 blossom 2.1.0blossom 2.1.0 is a feature release introducing some minor QOL features, and fixing handling of included files. It should be a straightforward upgrade for existing users of Blossom 2.0.1.
✨ Features
varianttemplate property when using variants by @jpenilla in https://github.com/KyoriPowered/blossom/pull/37🐛 Fixes
Full Changelog: KyoriPowered/blossom@v2.0.1...v2.1.0
v2.0.1: 🌼 blossom 2.0.1A hotfix release for blossom 2.0.0. See its release notes for information about the major changes in that release.
🐛 Fixes
Full Changelog: KyoriPowered/blossom@v2.0.0...v2.0.1
v2.0.0: 🌼 blossom 2.0.0NOTE 2.0.1 has been released as a hotfix to this version, resolving an issue with applying headers. See its release notes for details about those changes. We recommend using 2.0.1 instead, but the following release notes still provide helpful migration advice.
Blossom 2.0.0 is a complete redesign of the Blossom plugin to provide a fully featured solution for source and resource templating. It is based on the template engine used to build Sponge's
mathlibrary. See the README for an introduction to Blossom v2's features.Migrating from Blossom v1
The key difference in functionality with v2 is that only source files within the specific templates root will be processed as templates -- all other source files will have no other change.
This allows more efficient execution since templates only need to be regenerated when there are actual changes, and means that any compile errors in non-templated files will be linked correctly in IDE logs. Template output will also be exposed correctly to any IDE run configurations, since templates are processed at project import time.
The quickest migration from v1 starts with a buildscript like:
sourceSets { main { blossom { javaSources { // template values here property("token", value) } } } }Then place files that should be processed as templates in
src/main/java-templates. These are Pebble templates, so the variable syntax is{{ token }}. See their documentation for more of the language's features.Substitute
javawithgroovy,kotlin, orscalaas desired.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.