Closed fghaas closed 8 months ago
Hi @fghaas, currently this repo does not have a proper CI script in place. Tags are deployed manually.
We can certainly fix that situation but I'd like to gauge the importance/urgency. Could you just give us a hint of how you use GitHub tags from this repo in your own workflow? I understand that tags are one of the good practices of maintaining a repo, it's just a matter of setting the right priority for this issue.
EDIT: as a temporary quick fix, I manually pushed the missing v16.0.1 and v16.0.2 tags to GitHub.
I don't have a particular need for deploying from a tag, and if this isn't CI-ified it doesn't hurt much. It's just that I think you want to support both options to pip
-install a particular release — that is, from PyPI and from a Git repo. :)
Thank you!
Bug description
At the time of writing, the most recent release published on PyPI is 16.0.2, but this repo's tags stop at
v16.0.0
. It would be great to get thev16.0.1
andv16.0.2
tags in this repo, as well.Additional context
The Tutor repo had a practically identical issue — see https://github.com/overhangio/tutor/issues/856 — which required a fix to the CI scripts; I am guessing the same fix may be required here.