Skip to content

chore(clone): bump packageManager to pnpm@11.1.2 for OIDC publishing#39

Merged
ob-aion merged 1 commit into
mainfrom
chore/pnpm-11-oidc
May 15, 2026
Merged

chore(clone): bump packageManager to pnpm@11.1.2 for OIDC publishing#39
ob-aion merged 1 commit into
mainfrom
chore/pnpm-11-oidc

Conversation

@ob-aion
Copy link
Copy Markdown
Collaborator

@ob-aion ob-aion commented May 15, 2026

Summary

The 1.0.1 release failed with npm error code ENEEDAUTH. Root cause, verified against pnpm's release notes: npm OIDC trusted-publishing (the id-token exchange) landed in pnpm 11.0.7. clone was pinned to pnpm@10.33.0, where pnpm publish --provenance does the provenance attestation but not the OIDC token exchange — so a tokenless publish has no auth. No .npmrc value fixes this on pnpm 10.x.

Change

  • package.json packageManagerpnpm@11.1.2 (current latest 11.x; ≥ 11.0.7 required for OIDC)
  • pnpm-lock.yaml regenerated under pnpm 11 — still lockfileVersion: 9.0, no dependency changes (churn is the pnpm 11 writer reordering metadata)

Verified under pnpm 11.1.2

  • pnpm lint clean
  • pnpm typecheck clean
  • pnpm test — 97/97
  • pnpm build — ESM + CJS + dts emitted
  • CI green on this PR
  • After merge: re-tag 1.0.1 → OIDC + provenance publish succeeds (Trusted Publisher configured: coroboros/clone, ci.yml, no env)

pnpm OIDC trusted-publishing (the id-token exchange) landed in pnpm 11.0.7.
On the previous pnpm@10.33.0 pin, `pnpm publish --provenance` performed no
OIDC exchange and the tokenless release failed with ENEEDAUTH. Lockfile
regenerated under pnpm 11 (still lockfileVersion 9.0, no dependency changes).
Copy link
Copy Markdown
Collaborator Author

@ob-aion ob-aion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@ob-aion ob-aion merged commit 4e6c6ec into main May 15, 2026
5 checks passed
@ob-aion ob-aion deleted the chore/pnpm-11-oidc branch May 15, 2026 10:04
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