Repository navigation
ci(publish): push the release bump and tag with the click-ui-automation App - #1307
Flipmonster wants to merge 2 commits into
Conversation
…on App The release job's version-bump commit to main, the tag push and the release-notes edit now use a short-lived click-ui-automation App token instead of PAT_TOKEN. main is moving to required PR + review, and the App is on the org bypass list; a personal access token cannot be. The job runs in the `automation` environment, which holds the App key and admits main and v* tags. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Pass permission-contents (and permission-pull-requests where the job opens or merges PRs) to create-github-app-token, so the token does not inherit every permission of the installation (zizmor github-app audit). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Storybook Preview Deployed✅ Preview URL: https://click-i4gyf2pch-clickhouse.vercel.app Built from commit: |
Chromatic Storybook
Built from commit: Statuses as of the end of the run. The build link shows the live review state. |
What: the
publishjob's release steps now use a short-livedclick-ui-automationGitHub App token instead ofPAT_TOKEN: the version-bump commit tomain, the tag push, and the release-notes edit. The job runs in a newautomationenvironment, which holds the App key and allows onlymainandv*tags. Canary mode doesn't mint a token.Why: click-ui
mainis moving to required PR + review. It was dropped to level-1 because this push used a PAT. The App is on the org bypass list. A personal access token can't be.Check: a release dispatched from a branch other than
main, or a tag without thevprefix, won't get the key. Tell us if you use either.Before merge: Security applies the bypass (ClickHouse/security-integrations#6405). Please don't merge until then.
🤖 Generated with Claude Code