Process completed with exit code 1.

3) [chromium] › e2e/seo.spec.ts:224:1 › anonymous residential listing pages expose an indexable private-host teaser Error: expect(locator).toBeVisible() failed Locator: getByText('Resident of Newtown') Expected: visible Error: strict mode violation: getByText('Resident of Newtown') resolved to 2 elements: 1) <p>Resident of Newtown</p> aka getByText('Resident of Newtown', { exact: true }) 2) <p>Private Host is a resident of Newtown. Ask them f…</p> aka getByText('Private Host is a resident of') Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for getByText('Resident of Newtown') 240 | page.getByRole("heading", { name: "Private Host" }) 241 | ).toBeVisible(); > 242 | await expect(page.getByText("Resident of Newtown")).toBeVisible(); | ^ 243 | 244 | const pageHtml = await page.content(); 245 | for (const privateText of [ at /home/runner/work/peels/peels/e2e/seo.spec.ts:242:55

2) [chromium] › e2e/map.spec.ts:210:1 › map restores a localStorage-only view after hydration ──── Error: expect(received).toBeCloseTo(expected, precision) Expected: 1 Received: 0 Expected precision: 2 Expected difference: < 0.005 Received difference: 1 Call Log: - Timeout 5000ms exceeded while waiting on the predicate 89 | 90 | async function expectMapPinDetailScale(page: Page, expectedScale: number) { > 91 | await expect | ^ 92 | .poll( 93 | async () => 94 | page.getByTestId("map-view").evaluate((element) => { at expectMapPinDetailScale (/home/runner/work/peels/peels/e2e/map.spec.ts:91:3) at /home/runner/work/peels/peels/e2e/map.spec.ts:238:5

1) [chromium] › e2e/listings.spec.ts:89:1 › listing edit saves and restores seeded business fields Error: expect(locator).toHaveValue(expected) failed Locator: getByTestId('listing-write-form').locator('#description').first() Expected: "A demo business listing so local development exercises the multi-listing host views and badges." Received: "A demo business listing so local development exercises the multi-listing host views and badges.A demo business listing with a slightly different description for e2e coverage." Timeout: 5000ms Call log: - Expect "toHaveValue" with timeout 5000ms - waiting for getByTestId('listing-write-form').locator('#description').first() 9 × locator resolved to <textarea rows="6" required="" maxlength="640" autocorrect="on" id="description" spellcheck="true" data-headlessui-state="" class="yfLB0zj2 yfLB0zj4" autocapitalize="sentences" placeholder="Your donation details" aria-labelledby="headlessui-label-_R_1e2aav5ubsnpfdb_" aria-describedby="headlessui-description-_R_3e2aav5ubsnpfdb_">A demo business listing so local development exer…</textarea> - unexpected value "A demo business listing so local development exercises the multi-listing host views and badges.A demo business listing with a slightly different description for e2e coverage." 144 | 145 | await page.goto(BUSINESS_LISTING_EDIT_PATH); > 146 | await expect(listingWriteForm.locator("#description").first()).toHaveValue( | ^ 147 | originalDescription 148 | ); 149 | await expect(listingWriteForm.locator("#visibility").first()).toHaveValue( at /home/runner/work/peels/peels/e2e/listings.spec.ts:146:66

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, supabase/setup-cli@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/