docs: auto-inject release dates from git tags#1737
Merged
cpcloud merged 1 commit intoNVIDIA:mainfrom Mar 7, 2026
Merged
Conversation
Contributor
cpcloud
force-pushed
the
release-notes-date-stamp
branch
3 times, most recently
from
3839b9f to
2a19401
Compare
Contributor
Author
|
/ok to test |
Contributor
@cpcloud, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/ |
cpcloud
force-pushed
the
release-notes-date-stamp
branch
from
2a19401 to
1aa9c31
Compare
Contributor
|
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
Author
|
/ok to test |
Release notes no longer need a manual "Released on" line. The new release_date extension derives the date from the git tag at doc build time and injects it into the RST source for any release-notes page that doesn't already have one. Made-with: Cursor
cpcloud
force-pushed
the
release-notes-date-stamp
branch
from
1aa9c31 to
83e75e0
Compare
Contributor
Author
|
/ok to test |
This comment has been minimized.
This comment has been minimized.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release_date) that automatically injects "Released on" dates into release notes pages at doc build time, derived from git tags.cuda_python/docs/exts/directory, registered in all four packages'conf.py.How it works
When you write a new release notes file like
cuda_core/docs/source/release/0.8.0-notes.rst, just write the content -- skip the "Released on" line entirely. When the docs build runs after the git tag exists, the extension sees the filename0.8.0-notes, looks upcuda-core-v0.8.0in git, grabs the tag's creation date, and injects the date into the rendered output automatically.That last point means this is backward compatible with all existing release notes that already have manually written dates.