Consider cutting a new release?
namoshizun opened this issue · comments
Hi, the master branch has supported Django 5.0 and Python 3.11+ but the latest release is still 2 years ago. Could you cut a new release?
@dfunckt do you think we might be able to automate this with pypa/gh-action-pypi-publish and trusted publishing?
@federicobond I’ve already setup this action which is triggered every time a GitHub release is made.
To cut a new release we need a PR like #166 and a GitHub release after it’s merged. The action will then publish the release to PyPi.
@federicobond do you want to have a go at it? Otherwise I’ll do it later in the day.
Sure! I've just opened #188
Thank you! Let’s merge and see how publishing works, it’s been a while since the last release and might need updating.
Publishing failed -- I'm taking a look.
All done -- v3.4.0 has been published. Thank you @federicobond!
And thank you @namoshizun for prodding!