Commit 0440e4e
committed
ci(ecosystem): drop pnpm.overrides.playwright injection from patch-project.ts
Pre-version-bumping each project (so its lockfile resolves playwright >= 1.60
directly) is the right place to enforce the version — overriding it inside
patch-project.ts produced several pitfalls:
- pkg.pnpm.overrides is ignored by npm-managed projects (vitest-playwright-repro
uses npm); the override never reached the lockfile and the wedge returned
- override targeted the bare `playwright` package, missing vitepress which
depends on `playwright-chromium`
- writing pkg.pnpm before vp migrate flipped migrator branches and could mask
upstream pnpm-workspace.yaml overrides on forceFreshMigration projects
The repo.json `"playwright": true` flag still drives the workflow's
"Install Playwright chromium" step; the actual version pinning will be
handled at the upstream project level instead.1 parent feb29f7 commit 0440e4e
1 file changed
Lines changed: 0 additions & 16 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
35 | | - | |
36 | | - | |
37 | | - | |
38 | | - | |
39 | | - | |
40 | | - | |
41 | | - | |
42 | | - | |
43 | 27 | | |
44 | 28 | | |
45 | 29 | | |
| |||
0 commit comments