Playwright 1.64 waits for a Playwright MCP release built on it: the image keeps one Chromium for both #157
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#155 tried to move Playwright from 1.63.0 to 1.64.0 and the Playwright MCP from 0.0.80 to 0.0.83, and held both back. The MCP server must use the same Chromium revision as the image's Playwright, so it never downloads a browser mid-step (openspec-flow#17). Read from the packages'
browsers.jsonon 2026-10-08:What it needs
When an MCP release is built on a final Playwright 1.64.x with the same Chromium revision, move
PLAYWRIGHT_VERSIONandPLAYWRIGHT_MCP_VERSIONin theDockerfile,osf.config.PLAYWRIGHT_MCP_VERSION, and@playwright/testinui/package.jsonand its lockfile, together.Done when
The image's self-check reports the MCP server's Chromium at the image's revision and the browser subagent's server opens a page, and the fast lane's Playwright specs pass.
Still blocked upstream, checked against npm on 2026-10-16:
@playwright/mcpis still 0.0.83 (2026-09-28). It is built onplaywright-core1.64.0-alpha with Chromium 1247.No MCP release is built on a final 1.64.x yet, so the image keeps Playwright 1.63.0 and MCP 0.0.80, which share Chromium 1243.
Related, from #170:
project-playwright-browsersnow installs a project's own Playwright browsers into a writable cache on the state volume. So a project on 1.64 gets its own build, and no longer depends on this bump.Shipped in
4309dfe(merge49af5fc), live since 15:53Z on 2026-10-17, and archived in OpenSpec asplaywright-mcp-from-corein874eb27.No MCP release was ever built on a final 1.64.x, so the change took the other route: the MCP server is now
playwright mcp, from Playwright itself.browsersubagent's server is<playwright> mcp(4c12d8d).@playwright/mcpand its pin are gone, leaving one pin,PLAYWRIGHT_VERSION.OSF_PLAYWRIGHT_CLIreplacesOSF_PLAYWRIGHT_MCP.33ca45f), and one unit test keeps the Dockerfile,osf.configand the lockfile's versions in step (4c12d8d).4c12d8d,83f03ff).9da3eb1,bc4878c).Checked on production after
4309dfe:agent.judge.r3. Its first attempt used the browser, through three browser subagents, before an osfd restart cut it off; the second attempt judged from the first one's screenshot.find /var/lib/openspecflow/cache/ms-playwright -maxdepth 1 -xtype lprinted nothing: no link dangles. The 1248 builds are links into the image, and the 1243 builds are real folders, a project's own install, which osfd leaves alone.The deploy log's own lines weren't recorded. The deploy only tags an image
latestafter its self-check passes, so the check did pass. Closing.