1) [webkit] › e2e/tests/pages/contact.test.ts:138:3 › contact page › contact form › should display error message when sending contact form submission fails Error: expect(locator).toContainText(expected) failed Locator: getByRole('main').getByRole('alert') Expected substring: "Failed to send message." Received string: "" Timeout: 5000ms Call log: - Expect "toContainText" with timeout 5000ms - waiting for getByRole('main').getByRole('alert') 9 × locator resolved to <div role="alert" class="sr-only" aria-atomic="true" aria-live="assertive">…</div> - unexpected value "" 163 | 164 | await expect(contactPage.page.getByRole("main").getByRole("status")).toBeEmpty(); > 165 | await expect(contactPage.page.getByRole("main").getByRole("alert")).toContainText( | ^ 166 | "Failed to send message.", 167 | { timeout: statusTimeoutMs }, 168 | ); at /home/runner/work/knowledge-base/knowledge-base/apps/knowledge-base/e2e/tests/pages/contact.test.ts:165:73

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@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/

No files were found with the provided path: playwright-report/. No artifacts will be uploaded.

Use destructuring assignment for component props

A/an 'object expression' as default prop. This could lead to potential infinite render loop in React. Use a variable instead of 'object expression'

A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook

A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook

A/an 'object expression' passed as the value prop to the context provider should not be constructed. It will change on every render. Consider wrapping it in a useMemo hook

onSelect is only used inside 1 useEffect, which may be unnecessary. You can move the computation into useEffect directly and merge the dependency arrays

Do not use item index in the array as its key

Do not use item index in the array as its key

A context name must be a valid component name with the suffix 'Context'

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

1 flaky [webkit] › e2e/tests/pages/contact.test.ts:138:3 › contact page › contact form › should display error message when sending contact form submission fails 30 skipped 98 passed (2.2m)