Closed davfsa closed 2 years ago
That's my fault. The release action was buggy. It is fixed in #39. Once that is merged and v4.1.1 is tagged it should push a release to PyPI automagically.
@davfsa the CI fix was merged abd 4.1.1 is now available on pypi.
Tysm!
I have noticed that the project currently says it is on version
4.1.0
, and there is a tag and GitHub release with the same name, but there hasn't been a release on PyPI since3.0.0
.There seems to be a release CI setup, but it hasnt really worked from a quick look at the past runs. I will try to see the following days anything needs to be done to fix it (if its even broken).
Making this quick issue to bring it to your attention :)