1) [desktop-chromium] › tests/e2e/site-search.spec.ts:58:3 › site search dialog › arrow keys cycle through results, Tab keeps state, and Escape closes the dialog Error: expect(locator).toHaveAttribute(expected) failed Locator: locator('site-search dialog[open]').locator('.pagefind-ui__result-link').first() Expected: "true" Received: "" Timeout: 5000ms Call log: - Expect "toHaveAttribute" with timeout 5000ms - waiting for locator('site-search dialog[open]').locator('.pagefind-ui__result-link').first() 14 × locator resolved to <a role="option" aria-selected="false" id="aspire-search-target-0" href="/community/contributor-guide/" class="pagefind-ui__result-link svelte-4xnkmf">Contributor guide for aspire.dev</a> - unexpected value "null" 79 | 80 | // First result should auto-highlight as soon as Pagefind renders. > 81 | await expect(results.nth(0)).toHaveAttribute('data-search-active', 'true'); | ^ 82 | await expect(results.nth(0)).toHaveAttribute('aria-selected', 'true'); 83 | 84 | await expect(input).toBeFocused(); at /home/runner/work/aspire.dev/aspire.dev/src/frontend/tests/e2e/site-search.spec.ts:81:34

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

10 skipped 62 passed (1.5m)

8 skipped 64 passed (1.7m)