Skip to content

Bypass the pnpm version check when installing the linked js-sdk - #34906

Open
nathanael-h wants to merge 1 commit into
element-hq:developfrom
nathanael-h:chore/docker-link-repos-pnpm-bypass
Open

Bypass the pnpm version check when installing the linked js-sdk#34906
nathanael-h wants to merge 1 commit into
element-hq:developfrom
nathanael-h:chore/docker-link-repos-pnpm-bypass

Conversation

@nathanael-h

Copy link
Copy Markdown

scripts/docker-link-repos.sh clones matrix-js-sdk and runs pnpm install inside the clone. That clone pins its own pnpm version in devEngines.packageManager, which can differ from element-web's (currently 11.23.0). pnpm won't switch versions mid-process, so the install fails on the version guard rather than proceeding, and docker-bake / the linked-SDK Docker build stops there.

Set npm_config_pm_on_fail=ignore for the js-sdk install so the guard is bypassed instead of fatal. It's exported rather than passed as a CLI flag so it also covers the nested pnpm build that js-sdk's prepare lifecycle script spawns — that child process hits the same guard.

Scoped to the js-sdk clone only: element-web's own installs are untouched, so the pin still applies everywhere it should.

Split out of #32851 at review request — unrelated to that PR's feature work and purely devx.

Checklist

  • Tests written for new code (and old code if feasible).
  • New or updated public/exported symbols have accurate TSDoc documentation.
  • Linter and other CI checks pass.
  • I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

The cloned js-sdk may pin a different pnpm version than element-web, and
corepack won't switch versions mid-process. Export npm_config_pm_on_fail=ignore
so the linked install (and the nested pnpm build from js-sdk's prepare script)
proceeds instead of failing the version guard.
@nathanael-h
nathanael-h requested a review from a team as a code owner September 2, 2026 16:54
@github-actions github-actions Bot added the Z-Community-PR Issue is solved by a community member's PR label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Z-Community-PR Issue is solved by a community member's PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant