Workspaces / zero installs / yarn.lock

[RowanDZ]

Hi!

We make use of Yarn Berry, zero installs and workspaces.
Since we changed from yarn 1 to this setup, we see that our packages from workspaces end up in the yarn.lock file.

We'd like to know:

• What causes this? (Yarn Berry, or the zero installs?)
• Why is this happening?

We run into this issue because our cicd pipeline started failing in subsequent pipeline, after Lerna (what we use to version our monorepo packages) had published in a prior pipeline. This because your pipelines are running yarn --immutable --immutable-cache and clearly it fails because of the updated package versions.

Out of scope of this message, but it's solved by adding a script in the package.json:
"version": "echo 'Updating yarn.lock file after Lerna versioning' && yarn install --no-immutable --immutable-cache && git add yarn.lock",
which will be run by Lerna while it versions before publishing.

If somebody could bring clarity about this change, we'd appreciate it. :)