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 think that's SemVer-official, but Python/pip actually doesn't support the hyphen. From PEP 440:
Semantic versions containing a hyphen (pre-releases - clause 10) or a plus sign (builds - clause 11) are not compatible with this PEP and are not permitted in the public version field.
So, it's pretty common for folks to use the hyphenless prerelease identifier, even if it's not "real" semver. The Core team stumbled across this inconsistency a few months ago (dbt-labs/dbt-core#4741), and decided to let it be. The dbt-core semver logic supports both:
Prompted by @NiallRees's exciting
1.0.0b1
release ofdbt_artifacts
: https://github.com/brooklyn-data/dbt_artifacts/releases/tag/1.0.0b1hubcap/hubcap/version.py
Lines 14 to 15 in d82a8a2
I think that's SemVer-official, but Python/pip actually doesn't support the hyphen. From PEP 440:
So, it's pretty common for folks to use the hyphenless prerelease identifier, even if it's not "real" semver. The Core team stumbled across this inconsistency a few months ago (dbt-labs/dbt-core#4741), and decided to let it be. The
dbt-core
semver logic supports both:IMO:
1.0.0b1
and1.0.0-b1
as valid semantic version identifiers, with prerelease suffix b1.?
) to the regex stringThe text was updated successfully, but these errors were encountered: