feat: add "Coming Soon" to HoursStatus and HoursTable #700
yext-botmain-workflow.yml
on: pull_request
Matrix: call_build / build
automated_linting
/
linting
20s
update_notices
/
license-check
28s
Matrix: call_wcag / test
Matrix: update_snapshots / test
Matrix: call_test_matrix / matrix-test
Matrix: call_unit_test / unit_tests
Annotations
35 errors and 21 warnings
|
call_unit_test / unit_tests (24.x)
Process completed with exit code 1.
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > stays empty when coming soon is enabled:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L109
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:109:11
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > hydrates from the server-safe table to the client-aware table without warnings:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L60
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:60:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon template override without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L139
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:139:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon label without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L93
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:93:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates from the placeholder to the current status without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L49
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:49:11
|
|
call_unit_test / unit_tests (22.x)
The strategy configuration was canceled because "call_unit_test.unit_tests._24_x" failed
|
|
call_unit_test / unit_tests (22.x)
The operation was canceled.
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > stays empty when coming soon is enabled:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L109
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:109:11
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > hydrates from the server-safe table to the client-aware table without warnings:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L60
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:60:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon template override without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L139
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:139:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon label without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L93
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:93:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates from the placeholder to the current status without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L49
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:49:11
|
|
call_unit_test / unit_tests (20.x)
The strategy configuration was canceled because "call_unit_test.unit_tests._24_x" failed
|
|
call_unit_test / unit_tests (20.x)
The operation was canceled.
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > stays empty when coming soon is enabled:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L109
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:109:11
|
|
src/components/hours/hoursTable.hydration.test.tsx > HoursTable hydration > hydrates from the server-safe table to the client-aware table without warnings:
packages/pages-components/src/components/hours/hoursTable.hydration.test.tsx#L60
TypeError: act is not a function
❯ src/components/hours/hoursTable.hydration.test.tsx:60:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon template override without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L139
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:139:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates to the coming soon label without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L93
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:93:11
|
|
src/components/hours/hoursStatus.hydration.test.tsx > HoursStatus hydration > hydrates from the placeholder to the current status without warnings:
packages/pages-components/src/components/hours/hoursStatus.hydration.test.tsx#L49
TypeError: act is not a function
❯ src/components/hours/hoursStatus.hydration.test.tsx:49:11
|
|
update_snapshots / test (20.x)
Snapshot updates were made. A new commit with new snapshots was pushed.
|
|
call_test_matrix / Node 24 • React 19.2.3
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 24 • React 19.2.3
The operation was canceled.
|
|
call_test_matrix / Node 22 • React 18.2.0
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 22 • React 18.2.0
The operation was canceled.
|
|
call_test_matrix / Node 24 • React 18.2.0
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 24 • React 18.2.0
The operation was canceled.
|
|
call_test_matrix / Node 22 • React 19.2.3
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 22 • React 19.2.3
The operation was canceled.
|
|
call_test_matrix / Node 20 • React 18.2.0
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 20 • React 18.2.0
The operation was canceled.
|
|
main
Canceling since a higher priority waiting request for main-150 exists
|
|
main
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 20 • React 19.2.3
Canceling since a higher priority waiting request for main-150 exists
|
|
call_test_matrix / Node 20 • React 19.2.3
The operation was canceled.
|
|
automated_linting / linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, EndBug/add-and-commit@v9, pnpm/action-setup@v4.0.0. 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/
|
|
update_notices / license-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.1.6, actions/setup-node@v4.0.2, EndBug/add-and-commit@v9, pnpm/action-setup@v4.0.0. 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/
|
|
call_build / build (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, actions/upload-artifact@v4.3.3, pnpm/action-setup@v4.0.0. 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/
|
|
call_build / build (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, actions/upload-artifact@v4.3.3, pnpm/action-setup@v4.0.0. 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/
|
|
call_build / build (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, actions/upload-artifact@v4.3.3, pnpm/action-setup@v4.0.0. 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/
|
|
call_wcag / test (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_wcag / test (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_wcag / test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_unit_test / unit_tests (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/download-artifact@v4.1.7, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_unit_test / unit_tests (24.x)
Failed to restore: Cache service responded with 400
|
|
call_unit_test / unit_tests (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/download-artifact@v4.1.7, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_unit_test / unit_tests (22.x)
Failed to restore: Cache service responded with 400
|
|
call_unit_test / unit_tests (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/download-artifact@v4.1.7, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_unit_test / unit_tests (20.x)
Failed to restore: Cache service responded with 400
|
|
update_snapshots / test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.6, actions/github-script@v3, actions/setup-node@v4.0.2, EndBug/add-and-commit@v9, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 24 • React 19.2.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 22 • React 18.2.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 24 • React 18.2.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 22 • React 19.2.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 20 • React 18.2.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
|
call_test_matrix / Node 20 • React 19.2.3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4.1.6, actions/setup-node@v4.0.2, pnpm/action-setup@v4.0.0. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-output-20.x
|
43.8 KB |
sha256:c2ffa33bb6ecd914185a9326039d94f89eed9e5e457ae7bfc1a96ac8a8ef517a
|
|
|
build-output-22.x
|
43.8 KB |
sha256:f14de1f498db0ed6932cd54a9d1da85b61d42e2c641c7da01d964755a6ff9ffa
|
|
|
build-output-24.x
|
43.8 KB |
sha256:a5311ccce02322f7ec9f9a8ede4145dcc14209062cac9f32815b2612b772a2e4
|
|