Closed tseaver closed 2 months ago
You create and push the tag, which will build all binary packages. You yourself create the tarball and upload it. I always do bin/buildout setup setup.py sdist
followed by bin/twine upload dist/XXX.tar.gz
(I always have twine
right in my virtual environment)
And yes, an svb commit to cap it all off
/me wonders why we don't have the GHA workflow push the sdist
as well.
No idea, I didn't have the will to look into it yet and haven't been bothered too much.
@dataflake I was thinking about the new PyPI rules about tokens (they can't be scope to organizations, only projects, or else all projects).
Also, I almost uploaded a zope_interface-7.0.1.tar.gz
a moment ago, as I forgot that we have to build with a pinned setuptools
.
I have a command line expansion that sets up virtual environments with all those (stupid) pins in place so I hardly ever see that issue.
@dataflake I don't recall the current dance for making a release. Is it sufficient to push a 7.0.1 tag after this PR merges, followed by an
svb
commit?