Repository navigation
Conversation
The org doesn't let GITHUB_TOKEN create pull requests, so publish.yaml's repo job failed to open the v4.146.0 Helm/changelog PR, and update.yaml will fail to open the next "Update Code to X" PR. Both jobs now check out without persisted credentials, run their update script, then mint a coder-automations token (Cloud KMS) for coder/code-server only, and push and open the PR with it. update.yaml runs in the new main-only update environment; the repo job in release. GITHUB_TOKEN drops to contents: read. PRs opened by the App also trigger CI, which GITHUB_TOKEN-created ones didn't. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
setup-node caches the package manager's store by default, so a cache saved by another run could reach the job that publishes to npm. Turn it off there (zizmor cache-poisoning). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
code-asher
approved these changes
Nov 20, 2026
kylecarbs
enabled auto-merge (squash)
November 20, 2026 20:28
This branch has not been deployed
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.
The org doesn't let
GITHUB_TOKENcreate pull requests, so two jobs can't open their PRs:publish.yamlrepo(Helm chart and changelog after a release). v4.146.0's run pushedhelm/4.146.0, then failed withGitHub Actions is not permitted to create or approve pull requests. Update Helm chart and changelog with 4.146.0 #8152 was opened by hand.update.yaml(the scheduled "Update Code to X" PR, whichrelease.yamlreleases once merged). It will fail the same way on the next VS Code release.Both now:
persist-credentials: false, then run their update script with no write token around;coder-automationstoken through Cloud KMS, scoped tocoder/code-serverwith contents and pull-request write;gh auth setup-git, push the branch, and open the PR with that token.GITHUB_TOKENdrops tocontents: read.updateruns in a new main-onlyupdateenvironment, because the KMS pool only admits jobs that run in an environment.reporuns inrelease, whichpublish.yaml's other jobs already use. A side benefit: PRs opened by an App trigger CI, which PRs created byGITHUB_TOKENnever did.Merge after: coder/github-org-terraform#201 (the
updateenv) and coder/gcp#470 (letsupdate.yaml@maininupdatesign ascoder-automations) are applied, and theupdateenv has the three App secrets.coder-automationsis already installed on coder/code-server.actionlint is clean apart from existing shellcheck info notes. zizmor shows no new findings, and two fewer
artipackedwarnings.Also:
publish.yaml'snpmjob setspackage-manager-cache: falseonsetup-node. A cache saved by another run could otherwise reach the job that publishes to npm (zizmorcache-poisoning, high).🤖 Generated with Claude Code