Repository navigation
chore(example-apps): bump @playwright/test to 1.61.1 in dashmint-lab, dashnote, and dashproof-lab - #123
Conversation
… dashnote, and dashproof-lab These three apps locked Playwright 1.60.0 while dashrate and token-ops lock 1.61.1, so each version pulled its own Chromium build (~640 MB apiece). Playwright 1.60 also refuses to install browsers on Ubuntu 26.04, which the Docker Sandboxes agent image now uses; 1.61 supports it. All five apps now share one Playwright version and one Chromium build. Only @playwright/test, playwright, and playwright-core change in the lockfiles; regenerated with the .nvmrc Node (22.22.3, npm 10.9.8). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 44 minutes. View limit details
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
The apps declared different caret ranges (^1.59.1 or ^1.61.1), so a plain npm install or npm update in one app could pull a newer Playwright and its own Chromium build, letting the apps drift apart again. Pin the exact version everywhere, as the apps already do for @dashevo/evo-sdk, so Playwright upgrades are deliberate and made in all five apps together. Installed versions do not change: every lockfile already resolved 1.61.1. Only each package.json and the lockfile's root range change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
These three apps locked Playwright 1.60.0 while dashrate and token-ops lock 1.61.1, so each version pulled its own Chromium build (~640 MB apiece). Playwright 1.60 also refuses to install browsers on Ubuntu 26.04.
All five apps now share one Playwright version and one Chromium build. Only @playwright/test, playwright, and playwright-core change in the lockfiles; regenerated with the .nvmrc Node (22.22.3, npm 10.9.8).
Summary by CodeRabbit