You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using releases/* branches to check if my package is publishable on PyPI or not. Amongst others, I try to upload to TestPyPI.
The problem I'm facing is that even with version_scheme="release-branch-semver" all commits up to a tag are marked as development commit. Since they include a local identifier the upload is rejected. This is resolved after I create the tag, but I can't know beforehand if the upload will be rejected for another reason than the version.
My current workaround is to pre-install setuptools_scm and use get_version(version_scheme="release-branch-semver", local_scheme="no-local-version") to set SETUPTOOLS_SCM_PRETEND_VERSION.
Would it be possible to add a local_scheme that uses no-local-version while on a release/* branch and otherwise behaves as the default?
The text was updated successfully, but these errors were encountered:
It would be possible, my proposal however would be to have a env var which generally allows informed release pipelines to opt out of dev/local version tags to allow test artifact upload
I'm using
releases/*
branches to check if my package is publishable on PyPI or not. Amongst others, I try to upload to TestPyPI.The problem I'm facing is that even with
version_scheme="release-branch-semver"
all commits up to a tag are marked as development commit. Since they include a local identifier the upload is rejected. This is resolved after I create the tag, but I can't know beforehand if the upload will be rejected for another reason than the version.My current workaround is to pre-install
setuptools_scm
and useget_version(version_scheme="release-branch-semver", local_scheme="no-local-version")
to setSETUPTOOLS_SCM_PRETEND_VERSION
.Would it be possible to add a
local_scheme
that usesno-local-version
while on arelease/*
branch and otherwise behaves as the default?The text was updated successfully, but these errors were encountered: