Please make a new release and yank `0.16` due to blosc metadata bug

[tasansal]

Hello,

Based on #713 can you please make an urgent release and yank 0.16 from PyPI. We noticed this bug and we created many Zarr files with 0.16. Now we can't open any of the Zarr arrays when numcodecs!=0.16 with zarr-python or tensorstore.

@d-v-b pointed me to the above PR when we started running into this issue.

[joshmoore]

I've yanked 0.16.0. I'll defer to the team about cutting a new release.

[jonaslb]

The present situation (latest release yanked, no replacement) is even less fortunate. While before, datasets written with with the new numcodecs could be read by simply upgrading dependencies, now there is no way at all*. A speedy yank of a bad release might make sense to limit damage, but I think the chance for that has passed with 0.16 being released more than a month ago. At this point, the yank should follow the replacement release, not the other way around.

* - Manually editing the zarr metadata seems to work, but it's unfortunate that this is required.

[d-v-b]

sorry for the disruption @jonaslb, your feedback is very welcome here. we will get a new release out ASAP.

[d-v-b]

0.16.1 is released and pushed to pypi, please let us know if you run into any other problems here.