Skip to content

Accept post-release wheel versions in release validation#2178

Open
fallintoplace wants to merge 1 commit into
NVIDIA:mainfrom
fallintoplace:fix-post-release-wheel-validation
Open

Accept post-release wheel versions in release validation#2178
fallintoplace wants to merge 1 commit into
NVIDIA:mainfrom
fallintoplace:fix-post-release-wheel-validation

Conversation

@fallintoplace
Copy link
Copy Markdown
Contributor

Summary

  • reuse the release-note tag parser in validate-release-wheels
  • preserve .postN versions from release tags instead of truncating to X.Y.Z
  • add regression coverage for v12.6.2.post1 wheel validation

Why

Post-release tags such as v12.6.2.post1 were parsed as 12.6.2, so valid wheels like cuda_bindings-12.6.2.post1-...whl failed release validation before upload or publishing.

Testing

  • uvx pytest --confcutdir=ci/tools/tests ci/tools/tests/test_validate_release_wheels.py ci/tools/tests/test_check_release_notes.py
  • uvx ruff check ci/tools/validate-release-wheels ci/tools/tests/test_validate_release_wheels.py
  • uvx ruff format --check ci/tools/validate-release-wheels ci/tools/tests/test_validate_release_wheels.py
  • direct smoke test: ./ci/tools/validate-release-wheels v12.6.2.post1 cuda-bindings <tmp-wheel-dir>

@copy-pr-bot
Copy link
Copy Markdown
Contributor

copy-pr-bot Bot commented Jun 7, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions Bot added the CI/CD CI/CD infrastructure label Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant