:mega: `kotlinx-datetime` 0.7.1 is here, providing...
# kotlinx-datetime
d
📣
kotlinx-datetime
0.7.1 is here, providing a more convenient migration path to
kotlin.time.Instant
! https://github.com/Kotlin/kotlinx-datetime/releases/tag/v0.7.1
🎉 10
j
Are the 'compat' versions only for the 0.7.x series?
d
Are you asking if we going to publish
0.8.0-0.6.x-compat
as well? The current, optimistic plan is not to do that, but we'll decide based on the number of projects depending on
0.7.x-0.6.x-compat
.
j
Yes that was what I was asking. Since the 'compat' version is considered newer than the non-compat version according to semver and Gradle rules, tools like Renovate and dependabot try to update to them over the non-compat version.
d
Yeah, this is a known problem, but ordering them that way was necessary to allow
B
depending on
0.7.1
,
C
depending on
compat
, and
A
depending on both
B
and
C
without having to fix the dependency version to
compat
.
d
I tried using
0.7.1
alongside Exposed-beta-04 but its datetime support appears to be based on
0.6.2
and completely incompatible with this. What is this compat package mentioned above; could that make things work and why isn't it being mentioned in release notes if so? Turning back to
0.6.2
for now.
b
@Dmitry Khalanskiy [JB] Just a heads up...I believe material3 is bundled with compose and it is still using 0.6.x for kotlinx datetime. This results in a runtime crash on iOS when using
DatePicker
. It'd be great if compose 1.9.0 bumped the datetime library version used for material3
DatePicker
Would file a youtrack, but deploying a hotfix for my app is my last task before bedtime
👍 1
d