Repository navigation
Declare GITHUB_TOKEN permissions for workflows that write to the repo - #16652
Open
harryalbert wants to merge 1 commit into
Open
harryalbert wants to merge 1 commit into
harryalbert wants to merge 1 commit into
Conversation
Co-Authored-By: Warp <agent@warp.dev>
|
@harryalbert, your GitHub account is not connected to Warp. Connect your GitHub account. |
bnavetta
approved these changes
Oct 27, 2026
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.
Why
The warpdotdev enterprise default for
GITHUB_TOKENis moving to read-only (contents: read,packages: read,metadata: read). Workflows that comment on PRs, push branches/tags, create releases, or call reusable workflows requesting broader scopes need explicit grants, or they fail (reusable-workflow callers fail at run start). This adds the minimalpermissions:blocks, with a comment on each scope saying which step uses it.Changes
ci.yml:paramsjob getscontents: read(checkout) andpull-requests: read(dorny/paths-filterlists PR files via the API). This job gates the requiredCheck CI resultscheck. The other jobs only useGITHUB_TOKENfor API rate limiting or already declare permissions.populate_build_cache.yml: the caller ofci.ymlgrantscontents: read,id-token: write(tests jobs use GCP WIF), andpull-requests: read(params job). These are the scopes the callee's jobs request.create_release.yml: workflow-levelcontents: writecovers the release branch/tag push (checkout-persisted token),softprops/action-gh-release, and thegh release uploadsteps.cut_new_releases.yml/cut_new_release_candidate.yml: thecreate_release.ymlcallers grantcontents: write.delete_release.yml:contents: writeso the job can pushdeleted/<branch>and delete the original branch.check_approvals.yml:contents: read(checkout) andpull-requests: write(gh pr viewreviews,gh pr comment).repo-sync.yml:restack/approvecallers grantcontents: writeandpull-requests: write. Theescalationcaller grantsactions: write,contents: read, andpull-requests: write. These match the scopes the warpdotdev/repo-sync callee jobs declare.Of the 23 workflow files, 22 are byte-identical to the public
warprepo (ci.ymldiffers only by private repo-sync markers). Repo-sync will carry these changes there.actionlint: no new findings (126 pre-existing before and after).
CHANGELOG-NONE
Co-Authored-By: Warp agent@warp.dev
close_stale_fix_prs.yml,warp_cleanup_fix_prs.yml: deleted. Both clean up PRs created by theoz-agent-action"Fix Failing Checks" workflow (oz-agent-fix/run-*branches,auto-fix-cilabel), which this repo no longer runs. There are no open or recently closed PRs matching either, so the daily job has been a no-op. Deleting them instead of grantingpull-requests: writeto dead code.