Skip to content

fix(ci): also pin human-id via package.json for pnpm v8 (CI's pinned …#27

Merged
J-Ben merged 1 commit into
mainfrom
fix/release-human-id-esm
Jun 24, 2026
Merged

fix(ci): also pin human-id via package.json for pnpm v8 (CI's pinned …#27
J-Ben merged 1 commit into
mainfrom
fix/release-human-id-esm

Conversation

@J-Ben

@J-Ben J-Ben commented Jun 24, 2026

Copy link
Copy Markdown
Owner

…version)

CI uses pnpm@8 (pinned in the workflows), which reads overrides from package.json's "pnpm.overrides" field, not from pnpm-workspace.yaml's top-level "overrides" (that location only took effect in pnpm v10, the version installed locally). The Release workflow was still resolving human-id@4.2.0 despite the workspace override. Setting it in both places now covers CI's pnpm@8 and any future bump to pnpm v10+.

Summary

What does this PR do?

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Checklist

  • npm run build passes
  • npm run typecheck passes
  • npm test passes
  • Changeset added (npx changeset)

…version)

CI uses pnpm@8 (pinned in the workflows), which reads overrides from
package.json's "pnpm.overrides" field, not from pnpm-workspace.yaml's
top-level "overrides" (that location only took effect in pnpm v10, the
version installed locally). The Release workflow was still resolving
human-id@4.2.0 despite the workspace override. Setting it in both places
now covers CI's pnpm@8 and any future bump to pnpm v10+.
@J-Ben J-Ben merged commit 2dfbad5 into main Jun 24, 2026
3 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