Skip to content

fix: handle GitHub API rate limiting in build script and workflows - #1138

Draft
panavenue wants to merge 1 commit into
mainfrom
fix_macos_rate_limit_issue
Draft

fix: handle GitHub API rate limiting in build script and workflows#1138
panavenue wants to merge 1 commit into
mainfrom
fix_macos_rate_limit_issue

Conversation

@panavenue

Copy link
Copy Markdown
Collaborator

Title

fix: handle GitHub API rate limiting in build script and workflows

Description

Context & Problem

When running CI jobs (e.g., ./build.sh e2e_ci or ./build.sh lint_ci) or building locally, build.sh queries the GitHub REST API (such as api.github.com/repos/.../tags) to discover tool versions.

When unauthenticated API requests hit GitHub's 60 req/hr rate limit per IP, GitHub returns an error JSON payload ({"message": "API rate limit exceeded..."}).
Piping this response into jq -r '.[].name' resulted in the following error:

jq: error (at <stdin>:1): Cannot index string with string ("name")

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