Skip to content

fix: avoid GitHub API rate limits for the Node manifest - #1627

Open
BridgeAR wants to merge 1 commit into
actions:mainfrom
BridgeAR:BridgeAR/2026-09-03-setup-node-manifest
Open

fix: avoid GitHub API rate limits for the Node manifest#1627
BridgeAR wants to merge 1 commit into
actions:mainfrom
BridgeAR:BridgeAR/2026-09-03-setup-node-manifest

Conversation

@BridgeAR

@BridgeAR BridgeAR commented Sep 3, 2026

Copy link
Copy Markdown

Large matrices can exhaust the repository GITHUB_TOKEN rate limit because each cold manifest lookup resolves a repository tree and blob through REST.

This reads the fixed raw manifest path first and caches the nonempty response for later setup-node steps in the job. check-latest always bypasses that cache. The existing authenticated API path remains the fallback.

Refs: https://github.com/DataDog/dd-trace-js/actions/runs/33776938250/job/100720885063?pr=9406

Large job matrices exhaust the shared GITHUB_TOKEN rate limit because each cold manifest lookup resolves a repository tree and blob through the REST API.

Use the fixed raw manifest and reuse it within a job. check-latest always refreshes it, and the authenticated API remains a fallback.
@BridgeAR
BridgeAR marked this pull request as ready for review September 3, 2026 18:57
@BridgeAR
BridgeAR requested a review from a team as a code owner September 3, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants