navigation-compose-typed
navigation-compose-typed copied to clipboard
fix(deps): update kotlin & dokka & compose compiler
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| androidx.compose.compiler:compiler (source) | 1.5.13 -> 1.5.15 |
||
| org.jetbrains.kotlinx.binary-compatibility-validator | 0.14.0 -> 0.18.1 |
||
| org.jetbrains.kotlin.plugin.serialization (source) | 1.9.23 -> 1.9.25 |
||
| org.jetbrains.kotlin.android (source) | 1.9.23 -> 1.9.25 |
||
| org.jetbrains.kotlinx:kotlinx-serialization-json | 1.6.3 -> 1.9.0 |
||
| org.jetbrains.kotlin:kotlin-stdlib-jdk8 (source) | 1.9.23 -> 1.9.25 |
Release Notes
Kotlin/binary-compatibility-validator (org.jetbrains.kotlinx.binary-compatibility-validator)
v0.18.1
What's Changed
v0.18.0
What's Changed
- Supported KLIB cross compilation enabled in Kotlin 2.1.0 #299
- Fixed issue with early properties evaluation #286
- Started excluding local classes created by Parcelize #300
Thanks to @TheMrMilchmann, @osipxd, and @Goooler for their contributions!
v0.17.0
What's Changed
$suspendImplfunctions are now filtered from dumps (#271) This change may cause validation failures for projects where dumps already contain such functions. It is recommended to regenerate dumps (apiDumptask) after updating the BCV to0.17.0.- Supported class files generated for JVM target 23 (#284)
v0.16.3
What's Changed:
- Fixed support for Gradle version older than
8.2(#263)
v0.16.2
What's Changed:
- The plugin was changed to use the Gradle Workers API and its classpath isolation mode to remove almost all dependencies from the plugin itself; all required libraries are now fetched on demand, in isolation from the buildscript classpath (#208, #256, #258).
v0.16.0
What changed:
- Updated Kotlin Metadata JVM library to the latest version (now it's
kotlin-metadata-jvm:2.0.0) #255 - Various improvements in KLib ABI dumping API #253, #254
v0.15.1
What changed:
- Fixed a regression introduced in
0.15.0affecting how enum entries from classes with non-public companions are dumped (#250)
v0.15.0
This release finalizes what was added in the series of beta releases and adds Kotlin libraries (KLib) dumping and validation support. See project's README for details on how to enable it for your project.
The release contains some breaking changes that were made to align and fix BCV behavior across all supported configurations:
- BCV now (again) uses case-sensitive dump file names (#237);
- Multiplatform projects having no release sources (for instance, test-only projects) now need to be either explicitly excluded or an empty dump file needs to be generated for them (#231);
- Gradle tasks provided by the plugin changed their API to use Gradle Properties instead of plain Kotlin properties.
If any of these changes affect your projects, please check the migration guide for details on what needs to be done to update BCV to 0.15.0: 0.15.0 Migration Guide.
What changed:
From 0.15.0-Beta.3
- Non-public markers are now correctly handled when applied to
const vals (#90, #245) - Fixed KLib dump and validation behavior for empty projects (#246, #247); now
apiDumpwill emit an empty file andapiCheckwill successfully consume it
From 0.14.0 (brief overview of Beta.1 .. Beta.3 changes)
List<ClassBinarySignature>.dumpnow sorts declarations the same way the Gradle task does (#188)- API dump file names (for both JVM and Klib dumps) need to be case-sensitive (#231, #237)
- Validation behavior for empty projects was aligned across all supported configurations (#243, #244); now, such projects must either contain API dump files or be explicitly excluded using ignoredProjects.
- Experimental KLib ABI dumping and validation support was added (#183, #203, #196, #197, #234, #219, #214)
I want to give a shout-out to everyone involved! Special thanks to @benedekh, @adam-enko, @JakeWharton, @rickclephas, @lukellmann, @illarionov, @sandwwraith, @martinbonnin, @ilya-g and @shanshin for their feedback and contributions.
JetBrains/kotlin (org.jetbrains.kotlin.plugin.serialization)
v1.9.25: Kotlin 1.9.25
Note: This is a technical release for IntelliJ IDEA.
Changelog
Tools. JPS
KT-69204Generate lookups in dumb mode for compatibility with ref index
v1.9.24: 1.9.24
Changelog
Backend. Wasm
KT-64890K/Wasm compiler crash with external class and Kodein
Compiler
KT-65235JDK 21 might lead to change in overloads resolutionKT-66768K1: False positive UNRESOLVED_REFERENCE in super.getFirst/getLast call
Native
KT-67218Native: nested classes in kx.serialization ProtoBuf produce empty array for release binary
Tools. Gradle
Tools. Gradle. Multiplatform
KT-67127KMP: IDE Dependency Resolver for CInterops reports errors on linux and windows machinesKT-66514Don't get output file from Cinterop task for IDE Import if host os doesn't support it
Tools. JPS
KT-65043JPS dumb mode should respect maps needed for the compiler
Tools. Wasm
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.9.0
==================
This release updates Kotlin version to 2.2.0, includes several bugfixes and provides serializers for kotlin.time.Instant.
Add kotlin.time.Instant serializers
Instant class was moved from kotlinx-datetime library to Kotlin standard library.
As a result, kotlinx-datetime 0.7.0 no longer has serializers for the Instant class.
To use new kotlin.time.Instant class in your @Serializable classes,
you can use this 1.9.0 kotlinx-serialization version (Kotlin 2.2 is required).
You can choose between default InstantSerializer which uses its string representation,
or specify InstantComponentSerializer that represents instant as its components.
See details in the PR.
Other bugfixes
v1.8.1
==================
This release updates Kotlin version to 2.1.20, while also providing several important improvements and bugfixes.
Improvements
- Implemented encoding null in key and value of a map in Protobuf (#2910)
- Make type argument in JsonTransformingSerializer nullable (#2911)
- Use SPDX identifier in POMs (#2936) (thanks to Leon Linhart)
- Add watchosDeviceArm64 to Okio integration module (#2920) (thanks to Daniel Santiago)
- Update kotlinx-io version to 0.6.0 (#2933) (thanks to Piotr Krzemiński)
Bugfixes
- Fix incorrect enum coercion during deserialization from JsonElement (#2962)
- Supply proper equals(), hashCode(), and toString() for SerialDescriptor() wrapper (#2942)
- Do not encode empty packed collections in protobuf (#2907)
v1.8.0
==================
This release contains all of the changes from 1.8.0-RC. Kotlin 2.1.0 is used as a default, while upcoming 2.1.10 is also supported. Also added small bugfixes, including speedup of ProtoWireType.from (#2879).
v1.7.3
==================
This release aims to fix important issues that were discovered in the 1.7.2 release, including the inability to sync certain projects into Android Studio/IntelliJ IDEA and exceptions from custom Uuid serializers.
It uses Kotlin 2.0.20 by default.
- Use explicit kotlin-stdlib and kotlin-test versions from version catalog (#2818)
- Drop usage of deprecated Any?.freeze() in K/N target (#2819)
- Check against serialName instead of simpleClassName (#2802)
- Ignore NoClassDefFoundError when initializing builtins map for serializer() function (#2803)
- Clarify example for SerializationException (#2806)
v1.7.2
==================
This release provides several new features, including a major Cbor configuration rework. It uses Kotlin 2.0.20 by default.
Cbor feature set for COSE compliance
This change brings a lot of features to the CBOR format, namely:
- Serial Labels — see
@CborLabelannotation andpreferCborLabelsOverNamesflag. - Tagging of keys and values — see
encode*Tagsandverify*Tagsset of flags - Definite length encoding — see
useDefiniteLengthEncoding. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported. - Option to globally prefer major type 2 for byte array encoding — see
alwaysUseByteStringflag.
Since there are quite a lot of flags now, they were restructured to a separate CborConfiguration class, similarly to JsonConfiguration.
It is possible to retrieve this configuration from CborEncoder/CborDecoder interfaces in your custom serializers (see their documentation for details).
All of these features make it possible to serialize and parse COSE-compliant CBOR, for example, ISO/IEC 18013-5:2021-compliant mobile driving license data.
In case you want to make use of them, there is a predefined Cbor.CoseCompliant instance.
However, some canonicalization steps (such as sorting keys) still need to be performed manually.
This functionality was contributed to us by Bernd Prünster.
Keeping generated serializers
One of the most requested features for serialization plugin was to continue to generate a serializer even if a custom one is specified for the class. It allows using a plugin-generated serializer in a fallback or delegate strategy, accessing type structure via descriptor, using default serialization behavior in inheritors that do not use custom serializers.
Starting with this release, you can specify the @KeepGeneratedSerializer annotation on the class declaration to instruct the plugin to continue generating the serializer.
In this case, the serializer will be accessible using the .generatedSerializer() function on the class's companion object.
This annotation is currently experimental. Kotlin 2.0.20 or higher is required for this feature to work.
You can check out the examples in the documentation and in the PRs: #2758, #2669.
Serializer for kotlin.uuid.Uuid
Kotlin 2.0.20 added a common class to represent UUIDs in a multiplatform code.
kotlinx.serialization 1.7.2 provides a corresponding Uuid.serializer() for it, making it possible to use it in @Serializable classes.
Note that for now, serializer should be provided manually with @Contextual annotation.
Plugin will be able to automatically insert Uuid serializer in Kotlin 2.1.0.
See more details in the corresponding PR.
Other bugfixes and improvements
- Prohibited using of zero and negative field numbers in ProtoNumber (#2766)
- Improve readability of protobuf decoding exception messages (#2768) (thanks to xiaozhikang0916)
- docs(serializers): Fix grammatical errors (#2779) (thanks to jamhour1g)
- Fixed VerifyError after ProGuard optimization (#2728)
- Add wasm-wasi target to Okio integration (#2727)
v1.7.1
==================
This is a bugfix release that aims to fix missing kotlinx-serialization-hocon artifact.
It also contains experimental integration with kotlinx-io library.
Kotlin 2.0.0 is used by default.
Fixed HOCON publication
Sadly, 1.7.0 release was published incomplete: kotlinx-serialization-hocon artifact is missing from 1.7.0 and 1.7.0-RC releases.
This release fixes this problem and now kotlinx-serialization-hocon is available again with 1.7.1 version.
No other changes were made to this artifact. Related ticket: #2717.
Add integration with a kotlinx-io library
kotlinx-io is an official multiplatform library that provides basic IO primitives, similar to Okio.
kotlinx.serialization integration is now available in a separate artifact, located at the kotlinx-serialization-json-io coordinates.
Integration artifact provides functions similar to existing Okio integration: encodeToSink, decodeFromSource, and decodeSourceToSequence.
Check out the PR for more details.
Other bugfixes
- Prohibited use of elements other than JsonObject in JsonTransformingSerializer with polymorphic serialization (#2715)
v1.7.0
==================
This release contains all of the changes from 1.7.0-RC and is compatible with Kotlin 2.0. Please note that for reasons explained in the 1.7.0-RC changelog, it may not be possible to use it with the Kotlin 1.9.x compiler plugin. Yet, it is still fully backwards compatible with previous versions.
The only difference with 1.7.0-RC is that classDiscriminatorMode property in JsonBuilder is marked as experimental,
as it should have been when it was introduced (#2680).
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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.