Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 8 additions & 25 deletions sandbox/browser-web-v1/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion sandbox/browser-web-v1/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@
"type": "module",
"dependencies": {
"axe-core": "4.12.1",
"playwright": "1.62.0"
"playwright": "1.63.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟑 Browser environment descriptor stays stale

With playwright at 1.63.0, EVALUATION_ENVIRONMENT_V1 still declares 1.62.0. Environment contracts therefore misidentify the browser runtime. The package-policy consistency test also fails.

Learn more

The frozen evaluation descriptor is included in environment contract hashes by evaluateFrontendRun and catalog seeding. Updating the installed browser without updating the descriptor leaves those contracts describing a different Playwright release. The existing consistency test requires the package version, Playwright field, and bundled-browser field to match.

Example: A rebuilt template runs Playwright 1.63.0, while its evaluation policy records playwright: "1.62.0" and browser: "playwright-1.62.0-bundled-chromium".

Recommended fix: Update both EVALUATION_ENVIRONMENT_V1.playwright and EVALUATION_ENVIRONMENT_V1.browser to 1.63.0, then rebuild the evaluator template and refresh its configured build hash.

Devin Review

Was this helpful? React with πŸ‘ or πŸ‘Ž to provide feedback.

}
}
Loading