fix(release): make dev packages post-stable

Dev releases now use post-stable package versions in tasks/scripts/release.py:99:

  Python: 0.0.37.post108+g152d05940
  Cargo:  0.0.37+post.108.g152d05940
  Debian: 0.0.37+post.108.g152d05940-1
  RPM:    Version 0.0.37, Release 2.dev.108.g152d05940

That makes dev sort after the latest stable 0.0.37-1, while still sorting below
the next stable 0.0.38-1.

This allows us to do an upgrade installation from a stable release to a dev
release, but then still be able to upgrade that dev release to the next stable
release.

Signed-off-by: Kris Hicks <khicks@nvidia.com>
This commit is contained in:
Kris Hicks
2026-06-23 12:37:18 -07:00
parent 48a7d09e82
commit 9bbb670280
3 changed files with 19 additions and 27 deletions
+6 -6
View File
@@ -36,12 +36,12 @@ def test_exact_tag_versions_are_stable_release_versions() -> None:
def test_dev_versions_share_one_build_identity() -> None:
versions = release._versions_from_parts((0, 0, 37), 108, "152d05940", "v0.0.37")
assert versions.python == "0.0.38.dev108+g152d05940"
assert versions.cargo == "0.0.38-dev.108+g152d05940"
assert versions.docker == "0.0.38-dev.108-g152d05940"
assert versions.deb == "0.0.38~dev.108+g152d05940-1"
assert versions.rpm_version == "0.0.38"
assert versions.rpm_release == "0.dev.108.g152d05940"
assert versions.python == "0.0.37.post108+g152d05940"
assert versions.cargo == "0.0.37+post.108.g152d05940"
assert versions.docker == "0.0.37-post.108.g152d05940"
assert versions.deb == "0.0.37+post.108.g152d05940-1"
assert versions.rpm_version == "0.0.37"
assert versions.rpm_release == "2.dev.108.g152d05940"
def test_semver_tag_parser_excludes_vm_tags() -> None: