Update core libs, add API checks, expose contentWidnowsInsets on BottomSheetHost

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.jetbrains.kotlinx.binary-compatibility-validator	0.14.0 -> 0.16.3
org.jetbrains.kotlin.plugin.compose (source)	2.0.0 -> 2.0.20
org.jetbrains.kotlin.plugin.serialization (source)	2.0.0 -> 2.0.20
org.jetbrains.kotlin.android (source)	2.0.0 -> 2.0.20

---

Release Notes

Kotlin/binary-compatibility-validator (org.jetbrains.kotlinx.binary-compatibility-validator)

v0.16.3

Compare Source

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

Compare Source

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

Compare Source

What changed:

• Fixed a regression introduced in 0.15.0 affecting how enum entries from classes with non-public companions are dumped (#​250)

v0.15.0

Compare Source

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 (https://github.com/Kotlin/binary-compatibility-validator/pull/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 (https://github.com/Kotlin/binary-compatibility-validator/issues/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 apiDump will emit an empty file and apiCheck will successfully consume it

From 0.14.0 (brief overview of Beta.1 .. Beta.3 changes)

• List<ClassBinarySignature>.dump now sorts declarations the same way the Gradle task does (https://github.com/Kotlin/binary-compatibility-validator/pull/188)
• API dump file names (for both JVM and Klib dumps) need to be case-sensitive (https://github.com/Kotlin/binary-compatibility-validator/issues/231, https://github.com/Kotlin/binary-compatibility-validator/pull/237)
• Validation behavior for empty projects was aligned across all supported configurations (https://github.com/Kotlin/binary-compatibility-validator/issues/243, https://github.com/Kotlin/binary-compatibility-validator/pull/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.compose)

v2.0.20

v2.0.10: Kotlin 2.0.10

2.0.10

Apple Ecosystem

• KT-68257 Xcode incorrectly reuses embedAndSign framework when moving to and from 2.0.0

Compiler

Fixes

• KT-69876 K2 Compile exception: Only IrBlockBody together with kotlinx serialization
• KT-68521 K2: Property's private setters can be bypassed when using plusAssign and minusAssign operators
• KT-68667 K2: Compiler hangs on mapNotNull and elvis inside lambda
• KT-68747 K2: Long compilation time because of constraint solving when using typealias in different modules
• KT-68940 K2: "IllegalArgumentException: All variables should be fixed to something"
• KT-68797 K2 / Native: "java.lang.IllegalStateException: FIELD" caused by enabled caching
• KT-68362 False-positive ABSTRACT_MEMBER_NOT_IMPLEMENTED for inheritor of java class which directly implements java.util.Map
• KT-68449 K2: "when" expression returns Unit
• KT-67072 K2: inconsistent stability of open vals on receivers of final type
• KT-68570 K2: "Unresolved reference" in call with lambda argument and nested lambda argument
• KT-69159 K2: KotlinNothingValueException in Exposed
• KT-68623 K2: "Only safe or null-asserted calls are allowed" on safe call
• KT-68193 JDK 21: new MutableList.addFirst/addLast methods allow adding nullable value for non-null types
• KT-67804 removeFirst and removeLast return type with Java 21
• KT-68727 K2: "Null argument in ExpressionCodegen for parameter VALUE_PARAMETER" caused by an enum class with default parameter in a different module
• KT-68383 K2: "Argument type mismatch: actual type is 'kotlin.String', but 'T & Any' was expected." with intersection types
• KT-68546 K2: false-positive conflicting overloads error on inheriting generic type with inherited generic and non-generic member overloads
• KT-68626 K2: "Conflicting Overloads" for function if inherited from generic type
• KT-68351 K2: "Suspension functions can only be called within coroutine body"
• KT-68489 K2: WRONG_ANNOTATION_TARGET with Java and Kotlin @Target annotation positions
• KT-69058 K2: Java-defined property annotations not persisted
• KT-64515 K2 IDE: [NEW_INFERENCE_ERROR] in a build.gradle.kts script while applying "jvm-test-suite" plugin and then configuring targets for test suites
• KT-68016 K2: Gradle repo test should compile correctly with Kotlin explicit api mode fails on K2
• KT-68575 K2: @ParameterName annotation is not erased when inferring the type of it in lambdas
• KT-67999 K2: lost flexibility on parameters of Java SAM
• KT-59679 K2: Investigate extracting uncompleted candidates from blocks
• KT-68401 K2: "IllegalAccessError: failed to access class" caused by package private super Java type, when inferencing a common super type of if or when branches on JVM
• KT-68806 K/Wasm RuntimeError: unreachable on Sequence::toList
• KT-68455 K2: False negative UPPER_BOUND_VIOLATED_BASED_ON_JAVA_ANNOTATIONS
• KT-68538 KJS/K2: using while with break inside inline lambdas leads to an endless cycle
• KT-68798 JVM compiler crashes on calling private expect constructor with a default parameter
• KT-68734 K2: enum class in KMP: Expect declaration MMKVLogLevel is incompatible with actual MMKVLogLevel because modality is different
• KT-68674 False positive ACTUAL_WITHOUT_EXPECT in K2
• KT-68350 K2: "Inapplicable candidate(s)" caused by parameter reference of local class with type parameters from function
• KT-68571 K2: "IllegalStateException: Fake override should have at least one overridden descriptor" caused by exceptions and when statement
• KT-68523 K2: FileAnalysisException when using Definitely non-nullable types
• KT-68339 K2: "Enum entry * is uninitialized here" caused by lazy property with enum in when expression
• KT-66688 K2: false-negative "upper bound violated" error in extension receiver
• KT-68630 DiagnosticsSuppressor is not invoked with Kotlin 2.0
• KT-68222 K2. KMP. False negative Expected declaration must not have a body for expected top-level property with getter/setter
• KT-64103 FirExpectActualDeclarationChecker reports diagnostic error for KtPsiSimpleDiagnostic with KtFakeSourceElement
• KT-68191 K2. Static fake-overrides are not generated for kotlin Fir2IrLazyClass
• KT-68024 K2: Gradle repo test accessors to kotlin internal task types... fails on K2
• KT-64957 K1: drop ModuleAnnotationResolver

Compose compiler

• 0c5a858 Fix memoization of captureless lambdas when K2 compiler is used b/340582180
• a8249d6 Allow memoizing lambdas in composable inline functions b/340606661

Native

• KT-68094 K2/Native: Member inherits different '@Throws' when inheriting from generic type

Tools. Compiler Plugins

• KT-69187 Compose compiler for web doesn't support rememberComposableLambda
• KT-68557 K2. Supertypes resolution of KJK hierarchy fails in presence of allopen plugin

Tools. Compiler plugins. Serialization

• KT-68850 Compose lambda type not transformed with KGP 2 + new Compose plugin

Tools. Daemon

• KT-68297 KGP 2.0 regression: JAVA_TOOL_OPTIONS is not considered in Kotlin daemon creation

Tools. Gradle

• KT-69330 KotlinCompile friendPathsSet property is racy due causing build cache invalidation
• KT-69026 Mark AGP 8.5.0 as compatible with KGP
• KT-68447 ill-added intentionally-broken dependency source configurations
• KT-69078 Gradle: Add option to disable FUS Service
• KT-68278 Spring resource loading in combination with java-test-fixtures plugin broken
• KT-66452 Gradle produces false positive configuration cache problem for Project usage at execution time
• KT-68242 Run tests against AGP 8.4.0

Tools. Gradle. Multiplatform

• KT-68805 KMP project (re-)import took a long time for downloading platform libs
• KT-68248 kotlin multiplatform project fail to build on Fedora with corretto

Tools. Gradle. Native

• KT-68638 KGP 2.0 breaks native test with api dependencies and configuration cache
• KT-65761 Missing JDK Platform ClassLoader when compiling Kotlin native in daemon

Tools. JPS

• KT-69204 Generate lookups in dumb mode for compatibility with ref index

Tools. Kapt

• KT-68171 K2KAPT: boxed return types in overridden methods changed to primitives

Tools. Scripts

• KT-68681 K2 / CLI / Script: "NullPointerException: getService(...) must not be null" caused by @DependsOn
• KT-67747 K2: regression in Spring unit tests using javax.script.ScriptEngine

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

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 @CborLabel annotation and preferCborLabelsOverNames flag.
• Tagging of keys and values — see encode*Tags and verify*Tags set 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 alwaysUseByteString flag.

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 - "before 4am on Monday" (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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.