Repository navigation
ci(publish): push the release bump and tag with the click-ui-automation App - #1307
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>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7575631. Configure here.
The automation environment admits a run from main, but resolve and publish then checked out whatever branch the dispatch input or the release target named and ran its scripts with the App token. resolve now refuses any branch other than main for a release. app-id is deprecated in create-github-app-token; use client-id from the new CLICK_UI_AUTOMATION_CLIENT_ID repository variable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Hi @Flipmonster !
- publish.yml:227: a run from main with branch=foo passes the gate, then runs foo’s scripts with the App token. Please reject anything but main in resolve for the release path.
- publish.yml:218: app-id is deprecated. Please switch to client-id (needs a repo variable; I only have maintain).
The org tag floor refuses deleting or moving v* tags, and a new repo ruleset lets only maintainers, admins and click-ui-automation create them. Start over now keeps the tag: re-publish on it if main has not moved, else use the next version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Storybook Preview Deployed✅ Preview URL: https://click-gvjsoynvl-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
Note
Medium Risk
Changes how production releases authenticate and push to protected branches; misconfiguration of the App or environment could block releases or grant write access.
Overview
Release publishing no longer uses
PAT_TOKEN. Thepublishjob runs in a newautomationGitHub Environment, mints a short-livedclick-ui-automationApp token, and uses it for the release checkout, writing release notes, and (per existing release steps) pushing the version bump and tag—so automation can comply with required reviews onmain.A new “Guard - release from main only” step fails fast when a release is requested from a branch other than
main, and the manual workflow input description states that releases build frommainonly.docs/publish.mdis updated to match: only maintainers createv*tags,v*tags cannot be deleted under org rules (delete the release only), and “start over” explains reusing an existing tag vs bumping the version.Reviewed by Cursor Bugbot for commit 29f22d9. Bugbot is set up for automated code reviews on this repo. Configure here.