Skip to content

fix(setup-go): mint private-module token via create-github-app-token@v2 - #31

Merged
blairham merged 1 commit into
mainfrom
fix/setup-go-app-token-v2
Jul 2, 2026
Merged

fix(setup-go): mint private-module token via create-github-app-token@v2#31
blairham merged 1 commit into
mainfrom
fix/setup-go-app-token-v2

Conversation

@blairham

@blairham blairham commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Bumps the create-github-app-token used by setup-go's private-modules path from @v1@v2, matching pinpredict/k4a#112 (v1 is Node 20, forced to Node 24 with a warning; v2 is Node 24-native, input-compatible).

Now that k4a mints its private-module token through this composite (k4a#113), keeping the composite on v1 would reintroduce the Node 20 deprecation warning #112 removed. No-op for callers with private-modules at its default false.

🤖 Generated with Claude Code

v1 targets the deprecated Node 20 runtime (forced to Node 24 with a warning);
v2 is Node 24-native and input-compatible. Matches the v1->v2 bump k4a just
made for its inline token steps (pinpredict/k4a#112) — now that k4a mints
through this composite, keep it on v2 so the Node 20 deprecation warning
doesn't come back.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@blairham
blairham merged commit 691d0a8 into main Jul 2, 2026
2 checks passed
@blairham
blairham deleted the fix/setup-go-app-token-v2 branch July 2, 2026 22:34
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