Instead, we'll use a workflow that pulls the semver from each package's setup.py with a "dev{revision}" suffix. The revision number is retrieved from git describe --tags using the same process that setuptools_scm uses. When a commit has a tag associated with it, there will be no "dev{revision}" suffix applied.
This means we need to remember to increment the setup.py version number after each full release. If someone forgets to do this, pre-releases will be made for the previous version. Not ideal, but it won't break the existing stable release.
Unfortunately, setuptools_scm can't work with repositories that have multiple packages right now. Relevant issue: https://github.com/pypa/setuptools_scm/issues/357
Instead, we'll use a workflow that pulls the semver from each package's setup.py with a "dev{revision}" suffix. The revision number is retrieved from
git describe --tagsusing the same process that setuptools_scm uses. When a commit has a tag associated with it, there will be no "dev{revision}" suffix applied.This means we need to remember to increment the setup.py version number after each full release. If someone forgets to do this, pre-releases will be made for the previous version. Not ideal, but it won't break the existing stable release.