Skip to content

Upgrade kotlinx-datetime to 0.7.1 #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

ecstatic-morse
Copy link

This involves migrating to the builtin versions of a few types:

  • kotlinx.datetime.Instant -> kotlin.time.Instant
  • kotlinx.datetime.Clock -> kotlin.time.Clock

These are still experimental, so add the corresponding optIn flag as well.

simolus3
simolus3 previously approved these changes Jul 22, 2025
Copy link
Contributor

@simolus3 simolus3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@simolus3
Copy link
Contributor

Actually it looks like we'll have a hard time with this:

  1. Versions of the supabase-kt project older than 3.2.1 don't support the datetime migration yet (there are runtime failures about missing classes - java.lang.ClassNotFoundException: kotlinx.datetime.serializers.InstantIso8601Serializer).
  2. For me, updating supabase-kt to 3.2.1 resulted in compiler errors, probably because we need to upgrade our Kotlin version too.
  3. However, we're currently blocked on updating Kotlin due to SKIE 0.10.4 and Kotlin 2.2.0 can't create macOS frameworks touchlab/SKIE#162

Is this blocking something for you?

@ecstatic-morse
Copy link
Author

Not a blocker. This was just the last of my dependencies using version 0.6.x of kotlinx-datetime.

I mistakenly thought this only required kotlin >2.1.20 and kotlinx-serialization >1.9.0, but it looks like there's a bit more going on.

Feel free to put this on the pause until things settle down a bit.

@simolus3 simolus3 mentioned this pull request Aug 1, 2025
@simolus3 simolus3 closed this in #234 Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants