chore(e2e): upgrade @playwright/test 1.62.1 to 1.63.0 and dedupe playwright-core - #659
Merged
Merged
Conversation
…wright-core Dedupe playwright-core to a single 1.63.0. @axe-core/playwright stays 4.13.0. Chromium for the rendered-output suite is 153.0.8010.12. Refs #646
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
§11 order 10 now points at the PR that moves @playwright/test to 1.63.0.
This was referenced Sep 24, 2026
jasonhnd
added a commit
that referenced
this pull request
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #646
Part of #635 (order 10). Base
preview. Blocked-by order 9 is43d1e3b8(PR #658).Edits mapped to やること
chore/playwright-1.63.0fromorigin/preview43d1e3b8(order 9 merged). Bun 1.4.2 (1.4.2+744846f84) was already installed at/tmp/bun-1.4.2and was prepended toPATH. Global Bun was not upgraded (bun upgradewas not run;~/.bunwas not written). Nodev24.20.0. NoPUBLIC_GA4_MEASUREMENT_ID/PUBLIC_X_PIXEL_ID/PUBLIC_META_PIXEL_IDfor the CI-equivalent suite.package.jsondevDependencies["@playwright/test"]:"1.62.1"→"1.63.0"(exact, no caret).@axe-core/playwrightstays"4.13.0". Commit1d4ba5a9.bun install, thenbun update @axe-core/playwright. See Lockfile.bun x playwright test --reporter=line(noPUBLIC_*): 356 passed, 26 skipped, 0 failed.bun run test:e2eexited 1; see that section. Rendered-output assertions were not relaxed.1d4ba5a9sogit diff --exit-codeis the generated-file check.bun run test:e2erebuildsdist-astro/withPUBLIC_GA4_MEASUREMENT_ID=G-E2E0000000, so that build was replaced withbun run build(the same command as step 4,PUBLIC_*unset) beforeREQUIRE_BUILT_ARTIFACTSandverify:gates. All listed commands exit 0. Results match the dry-run table.1d4ba5a9:docs/TOOLCHAIN.md§2 Playwright/axe row:**1.63.0** / **4.13.0**(Chromium 153).CHANGELOG.md### Changed:- **@playwright/test 1.62.1 → 1.63.0 (Chromium 153)**; playwright-core deduped to one 1.63.0. CI rendered-output suite unchanged: 356 passed.docs/TOOLCHAIN.md§11 order 10:— done (#659). Follow-up commit5968e1e2.Lockfile
git diff --numstat 43d1e3b8for commit1d4ba5a9:package.jsondiff lines (git diff package.json | grep '^[-+] 'at the time of the bump, before the commit):bun install(Bun 1.4.2, after the pin bump, before dedupe):bun update @axe-core/playwright:The lockfile was written by those two commands. It was not hand-edited.
package.jsonaxe pin stayed"4.13.0".lockfileVersionstays 1.Lockfile greps (after dedupe)
@playwright/test@1.63.0depends onplaywright@1.63.0, which depends onplaywright-core@1.63.0. Oneplaywright-coreentry.fsevents lines in the same lockfile diff
playwright@1.63.0no longer declaresoptionalDependencies.fsevents.bun updaterewrote the lockfile's fsevents entries along with the playwright dedupe:fsevents2.3.2→2.3.3vite/fseventsalias removed (that alias was alreadyfsevents@2.3.3)package.jsondoes not namefsevents. The Issue's grep checks all match the dry-run table, so this was left as Bun wrote it.Verification (Bun 1.4.2+744846f84, Node v24.20.0, macOS arm64)
bun x playwright --versionbun x playwright install chromiumNode printed
Warning: The 'NO_COLOR' env is ignored due to the 'FORCE_COLOR' env being set.Progress bars omitted.bun run build(PUBLIC_* unset)The 844 route lines are omitted. CSP hashes unchanged.
bun x playwright test --reporter=line0 failed. Per-test lines omitted (382 listed: 356 passed + 26 skipped). This is the CI
qualitycommand. Counts match the dry-run table (356 passed / 26 skipped / 0 failed).bun run test:e2escripts/run-e2e.shranbun install --frozen-lockfile(no changes),bun x playwright install --with-deps chromium(browser already present), then rebuilt withPUBLIC_GA4_MEASUREMENT_ID=G-E2E0000000only. CSP hashes stayed 24 inline-script + 36 inline-style.git statusafter the run showed only the intendedpackage.json/bun.lockedits (docs were not written yet).All 10 failures are in
tests/e2e/analytics.spec.ts:analytics: … loads all tracker librarieson/,/sectors,/156,/rankings/ai-risk-low(mobile-chrome and desktop-chrome):Cloudflare Web Analytics beacon request was NOT made. Seen requests includegtag/js?id=G-E2E0000000and/_vercel/insights/script.js. Nostatic.cloudflareinsights.com/beacon.min.js.X Ads: window.twq becomes a function with non-empty pixel ID(mobile-chrome and desktop-chrome):page.waitForFunctiontimeout 8000ms.run-e2e.shsets only the throwaway GA4 id.PUBLIC_CF_BEACON_TOKENandPUBLIC_X_PIXEL_IDwere unset, soBaseLayout.astrodoes not emit the Cloudflare beacon or the Xtwqsnippet. The spec's file-level skip looks only forgoogletagmanager.com/gtag/jsindist-astro/sectors.html, so bakingG-E2E0000000un-skips the file and the other tracker assertions run.BaseLayout.astro,scripts/run-e2e.sh, andtests/e2e/analytics.spec.tsare unchanged versusorigin/preview. This is the localPUBLIC_*failure mode the Issue describes. Assertions were not relaxed, thresholds were not raised, and no spec was skipped.The CI-equivalent run above (no
PUBLIC_*) skipped those cases and matches the dry-run counts. A second full e2e onorigin/previewwith Playwright 1.62.1 was not executed.bun run typecheckbun run testbun run testrunsbuild:datathenbun test. ETL completed (556 occupations).sector.test.tsprints two[og] sectors projection schema mismatchlines. Same pre-existing negative fixtures noted on #657; the run is 1725 pass / 0 fail.REQUIRE_BUILT_ARTIFACTS=1 bun test scripts/home-css-loading.test.ts src/site/models-built.test.tsRun after the clean
bun run build(PUBLIC_*unset).bun run verify:gatesbun auditgit diff --exit-codeNo output. Working tree clean after the chain (no generated-file drift).
Not changed
playwright.config.ts, specs, and.github/workflows/ci.ymlare untouched.@axe-core/playwrightstays"4.13.0". No caret was added.lock,visible(), step subtitle/params) were adopted.Vercel
Read-only.
vercel inspectand the deployment build log. No state-changing Vercel command.1d4ba5a9(lockfile): GitHub statusDeployment has completed→dpl_2dnrgRA19AmUvg5R8iFR9HCeyGvW. Status Ready. Preview alias: https://jobs-git-chore-playwright-1630-zkscio.vercel.appbld_dgaphymmc, commit1d4ba5a):bun install --frozen-lockfile,bun install v1.4.1 (4661e494f),+ @playwright/test@1.63.0,[check-lockfile-sync] OK — 13 deps match between package.json and bun.lock.,1725 pass/0 fail,Build Completed in /vercel/output [49s].5968e1e2(§11 only):scripts/vercel-ignore-build.shskipped the build (Canceled by Ignored Build Step, deploymentGNa1ndrjSpxaoFhsJwMTqKPfMuav). That is the status on the PR head. It did not replace the deployment above.Build-image Bun is 1.4.1, which matches TOOLCHAIN §2 (Vercel
1.4.xobserved at 1.4.1).lockfileVersion1 installed under--frozen-lockfile.CI quality
Head run 36023910218 on
5968e1e2: jobqualitysuccess. The earlier run on1d4ba5a9was cancelled by the workflow concurrency group when the §11 commit was pushed.quality/ "Run rendered-output checks (a11y, §4.2 floor, layout invariants)":0 failed. Same pass count as the local run and the dry-run table.