source-academy / plugins / 28841853581

98%

feat/add-init-infra: 67%

push

github

ci: regenerate yarn.lock as part of the changesets version-bump step (#52)

* ci: regenerate yarn.lock as part of the changesets version-bump step

yarn changeset version only rewrites package.json/CHANGELOG.md, never
re-runs install. When it bumps a dependent's peerDependency range
(e.g. common-cse-machine >=0.1.0 -> >=0.2.0 in runner/web-cse-machine),
that leaves yarn.lock stale, which then fails the resulting "Version
Packages" PR's immutable install in CI (exactly what happened on #51).

Chain a plain "yarn install" after "yarn changeset version" so the
lockfile is always in sync in the same bot commit. It's a no-op when
nothing needs to change.

* ci: set YARN_ENABLE_IMMUTABLE_INSTALLS=false for the version-bump install

Matches changesets/action's own documented recommendation for the
"run yarn install after changeset version" pattern (see its README's
Yarn section) — without it this install could itself run in an
immutable/frozen mode and fail instead of doing its job.

11 of 13 branches covered (84.62%)

Branch coverage included in aggregate %.

38 of 38 relevant lines covered (100.0%)

3.97 hits per line