Skip to content

ci: upgrade npm before publish (OIDC needs npm >= 11.5.1) + checkout v7#6

Merged
jaredLunde merged 2 commits into
mainfrom
ci/upgrade-npm-for-oidc
Jun 20, 2026
Merged

ci: upgrade npm before publish (OIDC needs npm >= 11.5.1) + checkout v7#6
jaredLunde merged 2 commits into
mainfrom
ci/upgrade-npm-for-oidc

Conversation

@jaredLunde

Copy link
Copy Markdown
Contributor

The sdk/v0.1.0 run failed with ENEEDAUTH — node LTS ships npm 10, which doesn't support OIDC trusted publishing, so it fell back to token auth and found none. OIDC config on npm is fine; the CI npm was just too old.

  • add npm install -g npm@latest before npm publish (needs >= 11.5.1)
  • bump actions/checkout v6 -> v7 (latest)

After merge, re-tag to retrigger (the failed run didn't consume the version):
git tag -f sdk/v0.1.0 origin/main && git push -f origin sdk/v0.1.0

🤖 Generated with Claude Code

jaredLunde and others added 2 commits June 20, 2026 12:05
node LTS ships npm 10, which can't use OIDC trusted publishing and fails with
ENEEDAUTH. Upgrade to npm@latest (>=11.5.1) before npm publish. Also bump
actions/checkout v6 -> v7 (latest).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jaredLunde jaredLunde merged commit 2b9f9da into main Jun 20, 2026
5 checks passed
@jaredLunde jaredLunde deleted the ci/upgrade-npm-for-oidc branch June 20, 2026 19:33
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