In a checkout of this repo, tag 4.0.0 does not exist:
$ git tag | grep 4.0.0
4.0.0.dev0
In the list of tags on GitHub I do see 4.0.0. The tag is for commit b9566da, but that has a warning: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." This commit is from January 30.
But three weeks ago you really made a 4.0.0 release in commit 150a31a.
Do you know what could have happened?
Could you fix it? Not sure if you can remove a tag from GitHub if it does not really exist...
The effect can be seen in plone/meta#368: pre-commit autoupdate wants to update zpretty from 4.0.0 to 4.0.0.dev0 because that is the most recent tag.
Easiest fix might be to simply release 4.0.1 without any changes.
In a checkout of this repo, tag 4.0.0 does not exist:
In the list of tags on GitHub I do see 4.0.0. The tag is for commit b9566da, but that has a warning: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." This commit is from January 30.
But three weeks ago you really made a 4.0.0 release in commit 150a31a.
Do you know what could have happened?
Could you fix it? Not sure if you can remove a tag from GitHub if it does not really exist...
The effect can be seen in plone/meta#368:
pre-commit autoupdatewants to updatezprettyfrom 4.0.0 to 4.0.0.dev0 because that is the most recent tag.Easiest fix might be to simply release 4.0.1 without any changes.