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.
Similar to https://github.com/chronotope/chrono/issues/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
tzgit submodule is not updated after checkout.Chrono-tz 0.9.0 and chrono-tz-build 0.3.0
For the file
LICENSEthe crates.io packages have a text file with../LICENSEinstead 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.