Repository navigation
chore(release): support manual dispatch and /prepare-complete for complete prepare workflow - #4016
Merged
rickeylev merged 2 commits intoAug 8, 2026
Conversation
…plete prepare workflow Previously, the release preparation completion workflow only triggered automatically when a pull request with the `release-prepared` label was closed as merged. If the automatic trigger was missed or failed, maintainers had no mechanism to trigger completion on demand or update the release tracking issue checklist state. Support manual dispatch and comment-driven triggers with bidirectional issue/PR resolution. The workflow can now be invoked directly via manual dispatch, reusable workflow calls, or the `/prepare-complete` comment command on tracking issues and PRs. The release CLI tool resolves tracking issues and PRs from each other to mark the task complete in the tracking issue.
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.
Previously, the release preparation completion workflow only triggered
automatically when a pull request with the
release-preparedlabel wasclosed as merged. If the automatic trigger was missed or failed,
maintainers had no mechanism to trigger completion on demand or update
the release tracking issue checklist state.
Support manual dispatch and comment-driven triggers with bidirectional
issue/PR resolution. The workflow can now be invoked directly via
manual dispatch, reusable workflow calls, or the
/prepare-completecomment command on tracking issues and PRs. The release CLI tool
resolves tracking issues and PRs from each other to mark the task
complete in the tracking issue.