Skip to content

Implement and document a procedure for publishing timezone database information separately from the main release #524

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

Open
dkhalanskyjb opened this issue Apr 29, 2025 · 1 comment
Labels
timezone The model and API of timezones

Comments

@dkhalanskyjb
Copy link
Collaborator

The Wasm/WASI implementation of kotlinx-datetime uses the timezone database supplied by us (https://github.com/Kotlin/kotlinx-datetime?tab=readme-ov-file#note-about-time-zones-in-wasmwasi), as the platform itself does not expose the necessary data.

Someone may need to use newer versions of the timezone database while staying on the old version of kotlinx-datetime: for example, new versions may introduce unwanted behavior or remove the deprecated APIs, and the adaptation of the client code to the new version may be postponed. To support this, we need to be able to publish just the timezone database artifacts separately from the releases of the library itself.

@dkhalanskyjb dkhalanskyjb added the timezone The model and API of timezones label Apr 29, 2025
@dkhalanskyjb
Copy link
Collaborator Author

An extra research avenue: the mappings between Windows timezones and IANA timezone identifiers do occasionally get updated (example: https://github.com/Kotlin/kotlinx-datetime/pull/523/files), and they are also tied to the main library release at the moment. We may want to be able to somehow update them separately from the core library as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
timezone The model and API of timezones
Projects
None yet
Development

No branches or pull requests

1 participant