Update all non-major dependencies #134
Open
+6
−6
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:
4.3→4.3.10.35.0→0.36.05.4.0→5.5.01.5.5→1.6.01.5.5→1.6.01.9.0→1.10.09.3.0→9.3.1Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
v0.36.0Compare Source
BREAKING
DirectorySignatureTypeinternal.Behavior changes
validateDeploymentnow has theDeploymentValidationenum as type instead of being a boolean. The defaultis now to just wait for the
VALIDATEDstate. The previous behavior can be achieved by setting it toPUBLISHED.NONEcan be used for disabling the validation completely.configure(...)manually to configure what to publish and not passingjavadocJarexplicity,the plugin now defaults to publishing an empty javadoc jar.
Features
when using the default options and the Dokka plugin is applied to the project.
JavadocJarandSourcesJaroptions toconfigureBasedOnAppliedPluginsand to allapplicable project types that can be passed to
configure. The previousBooleanbased versions havebeen deprecated.
mavenCentralDeploymentValidationandmavenCentralAutomaticPublishingare used for the default values of the 2 parameters when they are not passedexplicitly. This allows to more easily override them in certain environments.
gradle.propertiesfiles are now considered inthe same way they are when isolated projects is disabled.
Improvements
Minimum supported versions
Compatibility tested up to
square/wire (com.squareup.wire:wire-runtime)
v5.5.0Compare Source
2026-01-12
Common
joshfriend/spotlight (com.fueledbycaffeine.spotlight:buildscript-utils)
v1.6.0BuildscriptParserProviderv1.5.6Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.10.0==================
This is a release candidate for 1.10.0 based on Kotlin 2.3.0. It stabilizes a set of frequently used JSON APIs and builder options,
adopts a new 'Return Value Checker' Kotlin feature, and provides a lot of improvements and bug fixes.
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
inteface, 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)GradleUp/shadow (com.gradleup.shadow)
v9.3.1Compare Source
Fixed
This fixes potential classpath conflicts when using Shadow with other plugins that also use ASM.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.