The following is the release procedure from the main branch to having the package on PyPI. Please be aware that access to these functions may be restricted on a user account basis.

• Ensure supported Python versions in pyproject.toml and noxfile.py are correct

• Ensure version is bumped in pyproject.toml and it is PEP440-compliant

Ensure CHANGELOG.md has been updated.

Create a new release. Add a new tag that matches the version in pyproject.toml. The release title must start with the exact version as well, followed by a brief description of the changes. Ensure that the release description contains all the relevant information, especially if there are breaking changes. The release description must link to the changelog.

Once a new release is created, publishing to PyPI happens automatically via a GitHub action. This action builds wheels for manylinux (both CLib 2.35 and 2.39), macOS and Windows. For all three platforms ARM-wheels are available, as well as x86 for Ubuntu and Windows. Source build is also released, be aware that this requires a C-compiler on the user side.

Check the status of the Publish Package GitHub action. Go to https://pypi.python.org/pypi/python-constraint/ and verify that new version is published. In addition, check in the managing section of PyPI if all wheels and the source distributions are correctly uploaded.