You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1ec3d88
Browse filesBrowse the repository at this point in the historyBrowse files
fix(javascript): vendor the pinned js-debug release without a GitHub API call (#867, #813)
build-js-debug.js asked api.github.com for the release's asset list before
downloading, and that lookup is subject to the unauthenticated REST quota
(60/h per IP). Shared CI runners and `docker build` (which carries no token)
run out of it: the COBOL Host job's postinstall vendoring and the daily
canary's image build both failed with 403.
vendor-manifest.json pins the tag AND the asset name, so the pinned build now
downloads straight from <upstream>/releases/download/<tag>/<asset> — served
by github.com, outside the API quota, the way vendor-codelldb.js already
does. 'latest' and version overrides still go through the API, and a direct
download that fails (an upstream re-release under another name) falls back
to it. The cobol-host job's install step also carries GITHUB_TOKEN, like the
other jobs' vendor step.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
**Installs and Docker builds no longer fail on the GitHub API rate limit** — vendoring the pinned js-debug release asked `api.github.com` for the release's asset list before downloading, and that lookup is subject to the unauthenticated quota of 60 requests per hour per IP: on a shared CI runner or inside a `docker build` (which has no token) it answered 403, failing the COBOL Host job's `pnpm install` and the daily published-artifact canary's image build. The pin in `vendor-manifest.json` already names the tag and the asset, so the vendoring now downloads it straight from `releases/download/`, which is outside the API quota — no token is needed for a pinned build. `JS_DEBUG_VERSION=latest` and version overrides still resolve through the API, and a direct download that fails falls back to it (#867, #813)
0 commit comments