chore(zarr-metadata): bump version to 0.1.1 - #3949
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3949 +/- ##
=======================================
Coverage 93.23% 93.23%
=======================================
Files 87 87
Lines 11696 11696
=======================================
Hits 10905 10905
Misses 791 791 🚀 New features to boost your workflow:
|
| @@ -1,2 +1,2 @@ | |||
| [build-system] | |||
| requires = ["hatchling>=1.29.0"] | |||
There was a problem hiding this comment.
we use https://github.com/ofek/hatch-vcs with a decent amount of success! This might explain why I think dev commit hashes are suffixed by default on to versions, hence my comment in #3935 (comment).
There was a problem hiding this comment.
We are also using vcs versioning but for zarr python. As this package is versioned independently, we will to add some logic to the git tag -> version string workflow to ensure that zarr python release tags are distinct from zarr metadata release tags
version 0.1.0 is burned on pypi in order to namesquat the package. so the first version we can publish will be 0.1.1.
TODO:
docs/user-guide/*.mdchanges/