release: add release notes guidance and cache tag tests - #139
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
guillon
force-pushed
the
dev/cguillon/release-note
branch
from
September 11, 2026 10:26
e7db65d to
fa0a4be
Compare
guillon
changed the title
Member
Author
|
@qaco merging it, you may comment later. |
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.
Motivation
Provide a consistent process for preparing GitHub release notes and avoid rerunning tests when a release tag points to a Git tree that has already passed CI.
Description
Add a Jinja2 release-note template covering important features, fixes, merged pull requests, and new contributors.
Document how to collect changes between tags, review generated Markdown, and publish release notes with the GitHub CLI.
Enable Git-tree-based test-result cache lookup and publication for tag builds. Package building, validation, and publication remain uncached.
Commits
docs: add release notes template and guidanceci: enable test result cache for tagsDiscussion
The tag test cache uses the same Git tree, operating system, and Python-version identity as branch and pull-request builds.
Testing:
actionlint .github/workflows/xtc-tests.ymlgit diff --checkTODO: