Build failure: vscode 1.136.0 (run 33747379489)

[github-actions]

Build failure on workflow run 33747379489.

• Triggered by: schedule
• VS Code tag: 1.136.0
• Run started: 2026-09-03T11:02:05.199Z

See the run for full logs.

[github-actions]

Starting fix attempt 1/5 in run https://github.com/bradford-tech/code/actions/runs/33747488193.
Triggering failure: https://github.com/bradford-tech/code/actions/runs/33747379489

[github-actions]

Fix PR #60 built green (run). Awaiting review/merge; this issue closes automatically when a release for the tag succeeds.

[github-actions]

Build failure on workflow run 33795347082.

• Triggered by: workflow_dispatch
• VS Code tag: 1.136.0
• Run started: 2026-09-03T19:31:50.346Z

See the run for full logs.

[github-actions]

Starting fix attempt 2/5 in run https://github.com/bradford-tech/code/actions/runs/33796968524.
Triggering failure: https://github.com/bradford-tech/code/actions/runs/33795347082

[claude]

Attempt 2 — this one needs a human hand; further bot attempts cannot fix it.

The build is not broken. Run 33795347082 built both targets green; #60 already fixed the 1.136.0 patches. The only failing job was Publish release + update versions pin, on a git push:

! [remote rejected] release/1.136.05923 (refusing to allow a GitHub App to create or
 update workflow `.github/workflows/claude-build-fix.yml` without `workflows` permission)

Root cause: the release branch is cut from the run’s checked-out SHA (42e1e60). Dependabot #58 merged to main at 19:16:45 — 82 seconds into a ~15-minute build — changing only workflow files. By push time the branch’s workflow files were a version behind main, and GitHub compares a pushed branch’s workflow files against the default branch (not the diff of the pushed commits), so it read as “updating a workflow.” GITHUB_TOKEN has no workflows permission and there is no workflows: key for permissions: to grant it.

Fix: cut the branch from current origin/main instead. Verified — see #61.

Why #61 is incomplete: the fix is a one-hunk edit to cron-build-and-release.yml, and the fix loop’s own claude[bot] token hits the same restriction (push rejected; contents API returns 403 Resource not accessible by integration). There is no transport available to this token, and moving the logic into a shell script would not help — the workflow must still be edited to call it.

So #61 carries the regression test and the docs, with the exact workflow hunk in its body for a human to apply. Attempts 3–5 will hit the identical wall, so please apply the hunk rather than re-dispatching the loop.

Worth considering: giving the release job a token with workflows permission would also unblock this loop next time.

[github-actions]

Fix PR #61 built green (run). Awaiting review/merge; this issue closes automatically when a release for the tag succeeds.

[github-actions]

Build + release succeeded for vscode 1.136.0 in https://github.com/bradford-tech/code/actions/runs/33804747866 (release 1.136.05924). Closing.