fix(deps): update all non-major dependencies#6
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
8e89518 to
6761e2c
Compare
6761e2c to
6bc4e6d
Compare
3487884 to
5508ec2
Compare
5508ec2 to
016bb7f
Compare
96f5bb0 to
69dbe37
Compare
bdb4afe to
f735a41
Compare
f735a41 to
b1724f6
Compare
be59355 to
df29aae
Compare
73023f8 to
e3e2258
Compare
e3e2258 to
737a0fc
Compare
9642817 to
d580cf5
Compare
873e0da to
3c9160a
Compare
cf5d81d to
5888989
Compare
5888989 to
35ac07c
Compare
4f5d912 to
c07ea97
Compare
c07ea97 to
859a779
Compare
8e4f76f to
c337d47
Compare
b92e4f4 to
c2c9f74
Compare
ba9fe0e to
d8e28c4
Compare
d8e28c4 to
9533180
Compare
This file contains hidden or 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
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:
9.1.0→9.3.17.0.7→7.0.141.5.18→1.5.321.9.0→1.10.02.2.0→2.3.102.2.0→2.3.10Release Notes
gradle/gradle (gradle)
v9.3.1: 9.3.1Compare Source
This is a patch release for 9.3.0. We recommend using 9.3.1 instead of 9.3.0.
The following issues were resolved:
Read the Release Notes
Upgrade instructions
Switch your build to use Gradle 9.3.1 by updating your wrapper:
See the Gradle 9.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.
v9.3.0Compare Source
v9.2.1: 9.2.1Compare Source
The Gradle team is excited to announce Gradle 9.2.1.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Björn Kautler,
hasunzo,
HYEON,
Hyunjoon Park,
HYUNJUN SON,
Jendrik Johannes,
Kirill Gavrilov,
Madalin Valceleanu,
Martin Bonnin,
Matthew Haughton,
Mikhail Polivakha,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Róbert Papp,
Simon Marquis,
TheGoesen,
Vincent Potucek,
Xin Wang.
Upgrade instructions
Switch your build to use Gradle 9.2.1 by updating your wrapper:
See the Gradle 9.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.
v9.2.0Compare Source
oshai/kotlin-logging (io.github.oshai:kotlin-logging)
v7.0.14Compare Source
What's Changed
New Contributors
Full Changelog: oshai/kotlin-logging@7.0.13...7.0.14
v7.0.13Compare Source
What's Changed
Full Changelog: oshai/kotlin-logging@7.0.12...7.0.13
v7.0.12Compare Source
What's Changed
Full Changelog: oshai/kotlin-logging@7.0.11...7.0.12
v7.0.11Compare Source
What's Changed
Full Changelog: oshai/kotlin-logging@7.0.10...7.0.11
v7.0.10Compare Source
Full Changelog: oshai/kotlin-logging@7.0.9...7.0.10
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.10.0==================
This release is based on Kotlin 2.3.0 and contains all of the changes from 1.10.0-RC.
The only additional change is a fix for ProtoBuf packing of Kotlin unsigned types (#3079).
Big thanks to KosmX for contributing the fix.
Stabilization of APIs
kotlinx-serialization 1.10 and subsequent releases will be focused on stabilization of existing APIs.
The following APIs and configuration options are no longer experimental because they're widely used without any known major issues:
Jsonconfiguration options:decodeEnumsCaseInsensitive,allowTrailingComma,allowComments, andprettyPrintIndent. (#3100)@EncodeDefaultannotation and its modes. (#3106)JsonUnquotedLiteralconstructor function (#2900)JsonPrimitiveconstructor function overloads that accept unsigned types. (#3117)JsonElementwithNothing?overloads. (#3117)Readiness for return value checker
Kotlin 2.3.0 introduces a new feature aimed
at helping you to catch bugs related to the accidentally ignored return value of the function.
kotlinx-serialization 1.10.0-RC code is fully marked for this feature, meaning that you
can get warnings for unused function calls like
Json.encodeToString(...).To get the warnings, the feature has to be enabled in your project as described here.
Polymorphism improvements
Polymorphic serialization received a couple of improvements in this release:
New
subclassesOfSealedutility to automatically register sealed subclasses serializers in polymorphic modules (#2201).Use it in your
SerializersModulewhen configuring a polymorphic hierarchy which contains both abstract and sealed classes.For example, when root of your hierarchy is an
interface, but most of your inheritors aresealedclasses.The new function will register all known sealed subclasses for you, so you don’t need to list them one by one.
This makes writing your
SerializerModules much faster and simpler.Big thanks to Paul de Vrieze for contributing this feature.
Class discriminator conflict check rework (#3105).
If a payload already contains a property with the same name as the configured discriminator (for example,
type),it is called a class discriminator conflict.
To produce a correct output and allow more inputs to be deserialized at the same time, the following changes were made:
JsonNamingStrategytransformations are now detected during serialization as well and will causeSerializationException.It also affects non-polymorphic classes.
ClassDisciminatorMode.ALL_JSON_OBJECTSandSerializersModuleBuilder.polymorphicDefaultSerializerare also detected.Previously, it was possible in the sealed hierarchies alone due to missing assertion. See #1664 for details.
General improvements
.serialNametoMissingFieldExceptionfor clearer diagnostics. (#3114)Automatic-Module-Nameentries for metadata JARs. (#3109)Bugfixes
BIGNUM_NEGATIVEtag name. (#3090)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 was generated by Mend Renovate. View the repository job log.