Recently, we accidentally created a liionpack release with the tag v.0.3.4 (which is not compatible with hatch-vcs). The tag was recently renamed to v0.3.4, creating some confusion for git (see how releases and tags are not in sequence, but still, the latest tag is v0.3.7).
https://github.com/pybamm-team/liionpack/pull/270 aims to migrate to hatch-vcs, but for some reason, hatch-vcs keeps on picking up the version v0.3.5 while installing liionpack, whereas, the latest version is v0.3.7.
Could you please let us know where we are going wrong? Thanks!
Thanks for creating this amazing library!
Recently, we accidentally created a
liionpack
release with the tagv.0.3.4
(which is not compatible withhatch-vcs
). The tag was recently renamed tov0.3.4
, creating some confusion forgit
(see how releases and tags are not in sequence, but still, the latest tag isv0.3.7
).https://github.com/pybamm-team/liionpack/pull/270 aims to migrate to
hatch-vcs
, but for some reason,hatch-vcs
keeps on picking up the versionv0.3.5
while installingliionpack
, whereas, the latest version isv0.3.7
.Could you please let us know where we are going wrong? Thanks!