Repository navigation
ci: open release PRs as the tailor-platform-pr-trigger app - #6
Merged
Merged
Conversation
jackchuka
marked this pull request as ready for review
November 9, 2026 03:42
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.
A PR opened with
GITHUB_TOKENdoes not trigger workflows, so CI on release PRs waited for someone to click Approve and run, and the requiredcicheck could not report on its own.The release workflow now mints a token for the
tailor-platform-pr-triggerapp (contents and pull requests write, already installed on this repo) and hands it to changesets/action, so the release PR is opened by the app and CI runs on it. npm publishing still uses OIDC.Needs the
PR_TRIGGER_APP_IDvariable and thePR_TRIGGER_APP_PRIVATE_KEYsecret, which tailor-inc/tailor-infra sets for this repo. Merge after that is applied.