Skip to content

Pass the job's read-only token to the AOT smoke step - #50

Merged
Mpdreamz merged 2 commits into
mainfrom
ci/smoke-token
Nov 12, 2026
Merged

Mpdreamz merged 2 commits into
mainfrom
ci/smoke-token

Conversation

@Mpdreamz

Copy link
Copy Markdown
Contributor

Fixes the 0.11.6 release run, whose osx-arm64 smoke test failed with API rate limit exceeded for 13.105.49.252. Hosted runners share IPs, so the 60 anonymous requests an hour ran out mid-run.

What

In CI the smokeaot step now receives the job's GITHUB_TOKEN (contents: read, masked in logs). The build script passes it to the three smoke commands as --token when it is set. Locally the step still runs anonymously.

Verify

  • ./build.sh smokeaot -s locally, without a token: passes (find-previous, current-version, generate).
  • The PR's linux-x64 AOT job runs the token path.
  • actionlint, zizmor and curb check: clean.

The 0.11.6 tag keeps the old step, so this ships as the next patch release.

🤖 Generated with Claude Code

The release run's osx-arm64 smoke failed with 'API rate limit exceeded for 13.105.49.252':
hosted runners share IPs, so the 60 anonymous requests an hour can run out mid-run. In CI the
smoke step now gets GITHUB_TOKEN (contents: read, masked in logs) and passes it as --token;
locally it still runs anonymously.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Mpdreamz Mpdreamz added the ci Build and automation (patch) label Nov 12, 2026
Make.Fs quotes each interpolated hole as one argument, so ' --token <t>' became part of the
--version value. The commands are now argument lists, and --token sits in the command text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Mpdreamz
Mpdreamz merged commit 1229bd0 into main Nov 12, 2026
5 checks passed
@Mpdreamz
Mpdreamz deleted the ci/smoke-token branch November 12, 2026 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Build and automation (patch)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant