Skip to content

tighten Supabase read access (#43) #305

tighten Supabase read access (#43)

tighten Supabase read access (#43) #305

Triggered via push May 12, 2026 01:56
Status Failure
Total duration 6m 42s
Artifacts 1

validate-app.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 2 warnings, and 1 notice
e2e-prod
Process completed with exit code 1.
[chromium] › e2e/seo.spec.ts:470:1 › signed-in private pages keep noindex metadata and route-specific titles: e2e/seo.spec.ts#L494
3) [chromium] › e2e/seo.spec.ts:470:1 › signed-in private pages keep noindex metadata and route-specific titles Error: expect(locator).toHaveAttribute(expected) failed Locator: locator('head meta[name="robots"]') Expected pattern: /noindex,\s*follow/ Timeout: 5000ms Error: element(s) not found Call log: - Expect "toHaveAttribute" with timeout 5000ms - waiting for locator('head meta[name="robots"]') 492 | }); 493 | await expect(page).toHaveTitle("Avery · Chats · Peels"); > 494 | await expect(page.locator('head meta[name="robots"]')).toHaveAttribute( | ^ 495 | "content", 496 | /noindex,\s*follow/ 497 | ); at /home/runner/work/peels/peels/e2e/seo.spec.ts:494:58
[chromium] › e2e/seo.spec.ts:224:1 › anonymous residential listing pages expose an indexable private-host teaser: e2e/seo.spec.ts#L242
2) [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
[chromium] › e2e/map.spec.ts:245:1 › map pins minify at country zoom: e2e/map.spec.ts#L268
1) [chromium] › e2e/map.spec.ts:245:1 › map pins minify at country zoom, then grow and animate selection Error: expect(locator).toBeVisible() failed Locator: getByTestId('map-pin').first() Expected: visible Timeout: 20000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 20000ms - waiting for getByTestId('map-pin').first() 266 | 267 | const firstPin = page.getByTestId("map-pin").first(); > 268 | await expect(firstPin).toBeVisible({ | ^ 269 | timeout: MAP_MARKER_RENDER_TIMEOUT_MS, 270 | }); 271 | await expectMapPinDetailScale(page, 0); at /home/runner/work/peels/peels/e2e/map.spec.ts:268:26
check
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/
e2e-prod
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/
🎭 Playwright Run Summary
3 failed [chromium] › e2e/map.spec.ts:245:1 › map pins minify at country zoom, then grow and animate selection [chromium] › e2e/seo.spec.ts:224:1 › anonymous residential listing pages expose an indexable private-host teaser [chromium] › e2e/seo.spec.ts:470:1 › signed-in private pages keep noindex metadata and route-specific titles 63 passed (2.5m)

Artifacts

Produced during runtime
Name Size Digest
playwright-artefacts
1.97 MB
sha256:c6e1355ea9ebf51bc33246a1046565d681c22044be189bc52043e06ec9946de6