Update all non-major dependencies (except core Kotlin) #141
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:
5.10.3
->5.11.4
0.18.3
->0.19.1
1.23.6
->1.23.7
2.23.1
->2.24.3
2.23.1
->2.24.3
0.5.0
->0.7.0
0.6.0
->0.6.1
3.17.6
->3.19
1.7.1
->1.8.0
1.7.1
->1.8.0
1.7.1
->1.8.0
3.9.0
->3.10.2
3.9.0
->3.10.2
Release Notes
ajoberstar/reckon (org.ajoberstar.reckon:reckon-gradle)
v0.19.1
Compare Source
NOTE: 0.19.1 is the same as 0.19.0. There was a publishing issue preventing 0.19.0 from getting out to Central.
This release makes commit message scope suppliers more flexible.
Use of
scopeSupplier = calcScopeFromCommitMessages()
allowed specifying the scope with a commit message likemajor: My Message
orpatch: My message
. However, there was a special case when the project hadn't reached 1.0.0 yet.Before a project reaches 1.0.0,
major:
prefixes were downgraded tominor
. The intent was to encourage breaking changes to still be committed asmajor:
for consistency, but respecting that reaching 1.0.0 is a more significant decision than just the first breaking change introduced into your code.The downside was that the only alternative to get to 1.0.0 was to use
-Preckon.scope=major
to supersede what the commit message supplier decided. This can be incompatible with many workflows that don't allow user interaction when reckon runs.With this release:
scopeSupplier = calcScopeFromCommitMessages()
now additionally supports amajor!:
prefix which ignores whether the project is pre-1.0.0 and forces use of the major scopescopeSupplier = calcScopeFromCommitMessageParser(BiFunction)
which allows custom logic to consider both the commit message and whether the project is pre-1.0.0 when it makes it's scope decisionscopeSupplier = calcScopeFromCommitMessages(Function)
continues to use the same pre-1.0.0 behavior when a major scope is returned for backwards compatibilityBreaking Changes
None
Enhancements
Fixes
Deprecations
None
Compatibility
Tested against the following versions.
detekt/detekt (io.gitlab.arturbosch.detekt:detekt-gradle-plugin)
v1.23.7
1.23.7 - 2024-09-08
This is a point release for Detekt
1.23.0
, built against Kotlin2.0.10
, with fixes for several bugs that got reported by the community.Notable Changes
Changelog
UndocumentedPublicProperty
- #7426public companion
object forUndocumentedPublicClass
- #7219Housekeeping/Docs
petertrr/kotlin-multiplatform-diff (io.github.petertrr:kotlin-multiplatform-diff)
v0.7.0
What's Changed
New Contributors
Full Changelog: petertrr/kotlin-multiplatform-diff@v0.6.0...v0.7.0
v0.6.0
What's Changed
Introduce Myers algorithm in linear space by @lppedd in https://github.com/petertrr/kotlin-multiplatform-diff/pull/112
chore(deps): update all github actions to v4 (major) by @renovate in https://github.com/petertrr/kotlin-multiplatform-diff/pull/99
Update Gradle to 8.6, switch to new Gradle GH actions by @petertrr in https://github.com/petertrr/kotlin-multiplatform-diff/pull/100
chore(deps): update dependency org.jetbrains.kotlin.multiplatform to v1.9.22 by @renovate in https://github.com/petertrr/kotlin-multiplatform-diff/pull/95
chore(deps): update detekt to v1.23.5 by @renovate in https://github.com/petertrr/kotlin-multiplatform-diff/pull/96
chore(deps): update junit to v5.10.1 by @renovate in https://github.com/petertrr/kotlin-multiplatform-diff/pull/94
chore(deps): update plugin org.ajoberstar.reckon.settings to v0.18.2 by @renovate in https://github.com/petertrr/kotlin-multiplatform-diff/pull/90
Update build configuration to reflect KGP improvements by @lppedd in https://github.com/petertrr/kotlin-multiplatform-diff/pull/102
Update codecov action to v4 by @petertrr in https://github.com/petertrr/kotlin-multiplatform-diff/pull/109
Perform an overall code cleanup by @lppedd in https://github.com/petertrr/kotlin-multiplatform-diff/pull/108
Support WebAssembly targets by @lppedd in https://github.com/petertrr/kotlin-multiplatform-diff/pull/111
Switch to the new Gradle action in release.yml by @petertrr in https://github.com/petertrr/kotlin-multiplatform-diff/pull/110
New Contributors
Full Changelog: petertrr/kotlin-multiplatform-diff@v0.5.0...v0.6.0
Kotlin/kotlinx-datetime (org.jetbrains.kotlinx:kotlinx-datetime)
v0.6.1
DateTimeFormat
(#405)/etc/localtime
set, defaulting toTimeZone.UTC
as the system time zone (#426)Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-properties)
v1.8.0
==================
This is a release candidate for the next version. It is based on Kotlin 2.1.0 and includes a few new features, as well
as bugfixes and improvements:
@JsonIgnoreUnknownKeys
annotationPreviously, only global setting
JsonBuilder.ignoreUnknownKeys
controlled whether Json parser would throw exception ifinput contained a property that was not declared in a
@Serializable
class.There were a lot of complaints that this setting is not
flexible enough.
To address them, we added new
@JsonIgnoreUnknownKeys
annotation that can be applied on a per-class basis.With this annotation, it is possible to allow unknown properties for annotated classes, while
general decoding methods (such as
Json.decodeFromString
and others) would still reject them for everything else.See details in the corresponding PR.
Stabilization of
SerialDescriptor
API and@SealedSerializationApi
annotationSerialDescriptor
,SerialKind
, and related API has been around for a long time and has proven itself useful.The main reason
@ExperimentalSerializationApi
was on SerialDescriptor's properties is that we wanted to discouragepeople from subclassing it.
Fortunately, Kotlin 2.1 provides a special mechanism for such a
case — SubclassOptInRequired.
New
kotlinx.serialization.SealedSerializationApi
annotation designates APIsas public for use, but closed for implementation — the case for SerialDescriptor, which is a non-sealed interface for
technical reasons.
Now you can use most of
SerialDescriptor
and its builders API without the need to opt-in into experimentalserialization API.
See the PR for more details.
Note: All
SerialKind
s are stable API now, exceptPolymorphicKind
— we may want to expand it in the future.Generate Java 8's default method implementations in interfaces
TL;DR This change ensures better binary compatibility in the future for library. You should not experience any
difference from it.
kotlinx.serialization library contains a lot of interfaces with default method implementations. Historically, Kotlin
compiled a synthetic
DefaultImpls
class for them.Starting from Kotlin 1.4,
it was possible to compile them using as Java 8's
default
methods to ensurethat new methods can still be added to interfaces without the need for implementors to recompile.
To preserve binary compatibility with existing clients, a special
all-compatbility
mode is supported in compilerto generate both
default
methods and syntheticDefaultImpls
class.Now, kotlinx.serialization finally makes use of this
all-compatibility
mode,which potentially allows us to add new methods to interfaces such as
SerialDescriptor
,Encoder
,Decoder
, etc.,without breaking existing clients. This change is expected to have no effect on existing clients, and no action from
your side is required.
Note that Kotlin 2.2 plans to enable
all-compatibility
mode by default.
Other bugfixes and improvements
is set to NONE (#2833)
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.
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:
@CborLabel
annotation andpreferCborLabelsOverNames
flag.encode*Tags
andverify*Tags
set of flagsuseDefiniteLengthEncoding
. This flag affects object encoding, since decoding of arrays with definite lenghts is automatically supported.alwaysUseByteString
flag.Since there are quite a lot of flags now, they were restructured to a separate
CborConfiguration
class, similarly toJsonConfiguration
.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.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
square/okio (com.squareup.okio:okio-fakefilesystem)
v3.10.2
Compare Source
2025-01-08
okio-nodefilesystem
artifact is no longer empty.v3.10.1
Compare Source
2025-01-07
FileSystem.close()
may prevent future access and/or clean up associated resources depending on the backing implementation.FakeFileSystem
will prevent future operations once closed.InputStream
s created fromBufferedSource.inputStream()
now have a more efficient version ofInputStream.transferTo()
which reduces memory copies.okio-nodefilesystem
is no longer publised as a JS project, but a Kotlin multiplatform project with only a JS target. This change should not affect consumers in any way, and is motivated by the Kotlin Gradle plugin deprecating the JS-only plugin.v3.10.0
Compare Source
2025-01-06
This version is equivalent to the subsequent 3.10.1, but it did not fully publish to Maven Central due to infrastructure problems.
v3.9.1
2024-09-12
Path.relativeTo
.Note: this artifact is only used in 'okio-fakefilesystem' and 'okio-nodefilesystem' and not in the Okio core.
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 is behind base branch, 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.