Skip to content

Give the GitHub token to espup in the ESP32 workflows - #37

Merged
strikeout merged 1 commit into
mainfrom
austin/esp32-ci-github-token
Oct 26, 2026
Merged

strikeout merged 1 commit into
mainfrom
austin/esp32-ci-github-token

Conversation

@strikeout

Copy link
Copy Markdown
Owner

Summary

The ESP32 CI on main stopped in the step "Install the Xtensa Rust toolchain". espup reads the latest Xtensa Rust version from the GitHub API, and the API returned 403 Forbidden. Without a token, the API allows 60 requests in an hour for each runner address.

espup sends the GITHUB_TOKEN variable as the Authorization header (github_query in src/toolchain/mod.rs of espup). The toolchain step of esp32-ci.yml and esp32-release.yml now sets it. The firmware code does not change.

Test

  • The ESP32 CI of this PR runs, because the PR changes .github/workflows/esp32-ci.yml.

The ESP32 CI on main stopped in the toolchain step. espup reads the
latest Xtensa Rust version from the GitHub API, and the API returned
403 Forbidden. Without a token, the API allows 60 requests in an hour
for each runner address.

espup sends the GITHUB_TOKEN variable as the Authorization header. The
toolchain step of the CI and the release workflow now sets it.
@strikeout
strikeout merged commit d272447 into main Oct 26, 2026
7 checks passed
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.

1 participant