pnpm lock file update

Affected Packages

Not sure.

Problem

When using pnpm with changesets in a monorepo, after merging the “Update Versions” PR from the changesets action, CI breaks on the “Install” step since changesets has updated the versions in linked packages but has not updated the pnpm-lock.yaml.

Proposed solution

I think after changesets updates linked package versions to the new/upcoming version, it should run pnpm install -r (recursive) to update the lock file. Not sure if there is a better solution or how pnpm itself is handling this issue. Thoughts @zkochan ?

[equinusocio]

On our side, we ended up using a custom sh script as temp fix:

- name: Create Release Pull Request or Publish to NPM
  id: changesets
  uses: changesets/action@v1
  with:
    version: ./update-lock.sh
    publish: npm run release

npx changeset version
npm i --package-lock-only

[jedrichards]

Just making a note regarding Yarn Berry behaviour, maybe of interest or help with Googling this issue for others … commonly on CI we run yarn install --immutable but this will fail on the Version Packages PR since that has amended the dependency versions without updating the lockfile and outputs the following failure:

The lockfile would have been modified by this install, which is explicitly forbidden.