You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to chronotope/chrono#1564 I verified the packages of past releases of chrono-tz and chrono-tz-build.
We had a couple of tags that differ from the releases. Some added by me past week, some because chrono-tz-build was tagged while it was released a few commits later together with chrono-tz. I updated those.
Chrono-tz 0.8.2
The crates.io package has the 2023b version of the time zone database. This can happen if the tz git submodule is not updated after checkout.
Chrono-tz 0.9.0 and chrono-tz-build 0.3.0
For the file LICENSE the crates.io packages have a text file with ../LICENSE instead of the contents of the file it symlinks to. I think this is caused by doing the release from a Windows system for which I did not go through the steps to enable symlink support.
The text was updated successfully, but these errors were encountered:
Similar to chronotope/chrono#1564 I verified the packages of past releases of chrono-tz and chrono-tz-build.
We had a couple of tags that differ from the releases. Some added by me past week, some because chrono-tz-build was tagged while it was released a few commits later together with chrono-tz. I updated those.
Chrono-tz 0.8.2
The crates.io package has the 2023b version of the time zone database. This can happen if the
tz
git submodule is not updated after checkout.Chrono-tz 0.9.0 and chrono-tz-build 0.3.0
For the file
LICENSE
the crates.io packages have a text file with../LICENSE
instead of the contents of the file it symlinks to. I think this is caused by doing the release from a Windows system for which I did not go through the steps to enable symlink support.The text was updated successfully, but these errors were encountered: