Commit 7bdc112
authored
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.1 parent 0fb0056 commit 7bdc112
1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
36 | | - | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
37 | 43 | | |
38 | 44 | | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
39 | 49 | | |
40 | 50 | | |
41 | 51 | | |
| |||
0 commit comments