Repository navigation
Consolidate and validate release automation - #308
Merged
Merged
Conversation
This was referenced Sep 12, 2026
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
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-branch workflow with one tag-based publisherrelease-candidateartifact on pull requests, main pushes, and manual runs without publishingVERSIONand require nonempty curated release notescontents: writeto the tag-only publishing jobThis supersedes #306 and #307 by including
softprops/action-gh-release@v3andactions/download-artifact@v8.0.1in the consolidated workflow.Validation
release-candidatedirectory was assembled locally from those real artifactsThe publishing job remains skipped on this PR. The new
Validate Release Inputsjob is the non-publishing end-to-end dry run.