Skip to content

CI: Check versioned release notes exist before releasing#1907

Open
cpcloud wants to merge 3 commits intoNVIDIA:mainfrom
cpcloud:issue-1326
Open

CI: Check versioned release notes exist before releasing#1907
cpcloud wants to merge 3 commits intoNVIDIA:mainfrom
cpcloud:issue-1326

Conversation

@cpcloud
Copy link
Copy Markdown
Contributor

@cpcloud cpcloud commented Apr 14, 2026

Summary

  • Adds a check-release-notes job to the release workflow that verifies the versioned release-notes file (e.g. 13.1.0-notes.rst) exists and is non-empty for each package being released
  • Blocks doc, upload-archive, and publish-testpypi jobs via needs: gates so releases cannot proceed with missing notes
  • .postN tags are silently skipped (no notes file expected)
  • Helper script at toolshed/check_release_notes.py with 20 pytest tests

Test plan

  • 20/20 pytest tests pass locally (tag parsing, component mapping, missing/empty/post detection, CLI exit codes)
  • Verify check-release-notes job runs in CI on a test release dispatch
  • Confirm .postN tags skip without failure

Closes #1326

🤖 Generated with Claude Code

@cpcloud cpcloud added this to the cuda.core v1.0.0 milestone Apr 14, 2026
@cpcloud cpcloud added P0 High priority - Must do! CI/CD CI/CD infrastructure labels Apr 14, 2026
@cpcloud cpcloud self-assigned this Apr 14, 2026
cpcloud and others added 3 commits April 14, 2026 18:15
Add a check-release-notes job to the release workflow that verifies
the versioned release-notes file (e.g. 13.1.0-notes.rst) exists and
is non-empty for each package being released. The job blocks doc,
upload-archive, and publish-testpypi via needs: gates.

Helper script at toolshed/check_release_notes.py parses the git tag,
maps component to package directories, and checks file presence.
Post-release tags (.postN) are silently skipped. Tests cover tag
parsing, component mapping, missing/empty detection, and the CLI.

Refs NVIDIA#1326

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Ensures the release-notes check validates the tagged tree, not the
default branch HEAD. Without this, manually triggered runs could
validate the wrong commit.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

@cpcloud cpcloud requested a review from leofang April 15, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure P0 High priority - Must do!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: The release workflow should check if the versioned release note is missing

1 participant