Open dbeatty10 opened 6 months ago
All tags that conform to SemVer 2.0.0 will work. ✅
But not all tags that conform to PEP 440 will work. ❌
As mentioned in https://github.com/dbt-labs/hubcap/issues/129, the hubcap.py script requires tag versions that adhere strictly to SemVer 2.0.0. So alphas, betas, release candidates, etc. require a format like these:
hubcap.py
3.0.0-dev.3
2.0.0-rc10
1.0.0-b1
0.1.0-a2
There are version specifiers that are valid in PEP 440 but not able to be accepted by hubcap.py like these:
3.0.0dev.3
2.0.0rc10
1.0.0b1
0.1.0a2
We want to document this so that we have something to point to and gives guidance to package maintainers.
We could choose to adopt the functionality described in https://github.com/dbt-labs/hubcap/pull/130 instead.
TLDR
All tags that conform to SemVer 2.0.0 will work. ✅
But not all tags that conform to PEP 440 will work. ❌
More detail
As mentioned in https://github.com/dbt-labs/hubcap/issues/129, the
hubcap.pyscript requires tag versions that adhere strictly to SemVer 2.0.0. So alphas, betas, release candidates, etc. require a format like these:3.0.0-dev.32.0.0-rc101.0.0-b10.1.0-a2There are version specifiers that are valid in PEP 440 but not able to be accepted by
hubcap.pylike these:3.0.0dev.32.0.0rc101.0.0b10.1.0a2We want to document this so that we have something to point to and gives guidance to package maintainers.
Alternatives considered
We could choose to adopt the functionality described in https://github.com/dbt-labs/hubcap/pull/130 instead.