feat: [UIE-10778], [UIE-10777] - IAM LA/New flag fix, text update #35654
ci.yml
on: pull_request
test-manager
26m 15s
test-utilities
42s
test-queries
23s
test-shared
36s
typecheck-ui
42s
typecheck-utilities
24s
typecheck-queries
25s
typecheck-shared
56s
typecheck-manager
2m 13s
publish-packages
0s
publish-storybook
0s
Annotations
5 errors and 23 warnings
|
test-manager
Process completed with exit code 1.
|
|
src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx > DestinationCreate > when customHttpsEnabled feature flag is set to true > and Destination Type is set to Custom HTTPS > given Test Connection and Create Destination buttons > when form properly filled out and Test Connection button clicked and connection verified negatively > should not enable Create Destination button:
packages/manager/src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx#L728
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx:728:11
|
|
src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx > DestinationCreate > when customHttpsEnabled feature flag is set to true > and Destination Type is set to Custom HTTPS > given Test Connection and Create Destination buttons > when form properly filled out and Test Connection button clicked and connection verified positively > should enable Create Destination button and perform proper call when it's clicked:
packages/manager/src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx#L687
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx:687:11
|
|
src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx > DestinationCreate > when customHttpsEnabled feature flag is set to true > and Destination Type is set to Custom HTTPS > HTTPS Headers fields > Custom Headers > should update custom header title when Name is typed:
packages/manager/src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx#L451
TestingLibraryElementError: Unable to find an element with the text: Custom HTTPS. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.
Ignored nodes: comments, script, style
<body
data-theme="light"
>
<div>
<div
class="MuiGrid-root MuiGrid-container MuiGrid-direction-xs-row css-1quvjvd-MuiGrid-root"
data-qa-entity-header="true"
>
<div
class="MuiGrid-root MuiGrid-direction-xs-row css-17fpwt7-MuiGrid-root"
>
<div
class="css-13hlpjo-StyledRootDiv"
>
<div
class="css-t20r5x-StyledDiv"
>
<div
class="css-1ls2ac2-StyledDiv"
>
<a
aria-label="Delivery "
class="css-9867l-root"
data-qa-link="true"
data-testid="internal-link"
href="/logs/delivery/destinations"
>
<p
class="MuiTypography-root MuiTypography-body1 css-1xij3l3-MuiTypography-root-StyledTypography"
data-qa-link-text="true"
data-testid="link-text"
>
Delivery
</p>
</a>
<p
class="MuiTypography-root MuiTypography-body1 css-7m0bep-MuiTypography-root-StyledSlashTypography"
>
/
</p>
</div>
<div
class="css-67xfb3-StyledDiv"
>
<h1
class="MuiTypography-root MuiTypography-h1 css-1cdiahs-MuiTypography-root-StyledH1Header"
data-qa-header="Create Destination"
tabindex="0"
>
Create Destination
</h1>
</div>
</div>
</div>
</div>
<div
class="MuiGrid-root MuiGrid-direction-xs-row css-17fpwt7-MuiGrid-root"
>
<div
class="MuiGrid-root MuiGrid-direction-xs-row css-8jw8ki-MuiGrid-root"
>
<a
aria-label="Docs - link opens in a new tab"
class="docsButton css-uf80la-root-StyledDocsLink"
data-testid="external-link"
href="https://techdocs.akamai.com/cloud-computing/docs/log-delivery"
rel="noopener noreferrer"
target="_blank"
>
<svg
fill="none"
height="16"
viewBox="0 0 16 16"
width="16"
xmlns="http://www.w3.org/2000/svg"
>
<path
clip-rule="evenodd"
d="M4.22023 2.88685C4.06356 3.04352 3.99834 3.21624 3.99834 3.33329V11.3725C4.02276 11.3675 4.04596 11.3633 4.06776 11.3596C4.13799 11.3479 4.19796 11.3418 4.24299 11.3386C4.26561 11.337 4.28478 11.3361 4.29995 11.3356L4.31974 11.3351L4.32733 11.335L4.33054 11.335L4.33199 11.335C4.33232 11.335 4.33333 11.335 4.33333 11.9946V11.335H12.0017L12.0017 3.3333C12.0017 3.21624 11.9364 3.04352 11.7798 2.88685C11.6231 2.73018 11.4504 2.66496 11.3333 2.66496H4.66667C4.54961 2.66496 4.3769 2.73018 4.22023 2.88685ZM13.3317 11.9999V3.33329C13.3317 2.78368 13.0636 2.28973 12.7202 1.9464C12.3769 1.60307 11.8829 1.33496 11.3333 1.33496H4.66667C4.11706 1.33496 3.62311 1.60307 3.27978 1.9464C2.93645 2.28973 2.66833 2.78368 2.66833 3.33329V13C2.66833 13.3663 2.76184 13.6853 2.93627 13.947C3.10793 14.2045 3.33205 14.3678 3.53594 14.4698C3.73722 14.5704 3.93046 14.6174 4.06776 14.6403C4.13799 14.652 4.19796 14.6581 4.24299 14.6613C4.26561 14.6629 4.28478 14.6638 4.29995 14.6643L4.31974 14.6648L4.32733 14.6649L4.33054 14.665L4.33199 14.665C4.33232 14.665 4.33334 14.665 4.33333 14L4.33338 14.665H12.6667C13.0339 14.665 13.3317 14.3672 13.3317 14C13.3317 13.6327 13.0339 13.335 12.6667 13.335H12.6653L12.665 12.665H12.6667C13.0339 12.665 13.3317 12.3672 13.3317 11.9999ZM11.335 13.335H4.3425L4.33774 13.3347C4.32808 13.334 4.30993 13.3323 4.28641 13.3284C4.23621 13.32 4
|
|
src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx > DestinationCreate > when customHttpsEnabled feature flag is set to true > and Destination Type is set to Custom HTTPS > HTTPS Headers fields > Custom Headers > should add a custom header when clicking Add Custom Header button and allow typing in Custom Header fields:
packages/manager/src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx#L596
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/features/Delivery/Destinations/DestinationForm/DestinationCreate.test.tsx:596:11
|
|
test-search
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/ui)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/utilities)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/validation)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/api-v4)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/shared)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
build-validation
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (@linode/queries)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-ui
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-sdk
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
build-sdk
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-queries
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
typecheck-utilities
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
typecheck-queries
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
validate-sdk
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-shared
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
typecheck-ui
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-utilities
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
lint (linode-manager)
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
typecheck-shared
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
typecheck-manager
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
build-storybook
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
|
|
test-manager
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/download-artifact@v4, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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 | |
|---|---|---|---|
|
packages-api-v4-lib
|
408 KB |
sha256:3de45064d4af558000f5ed2fdbe56ad37eb400f34ff1cd8c2dfaf5488b1799c1
|
|
|
packages-validation-lib
|
164 KB |
sha256:1ed4a99e3516ea621f875fe30524d9aab665e76f4287690367e9a3024256baf0
|
|
|
storybook-build
|
13 MB |
sha256:872533a6f7d5caba7a0deca165e512faaca958a72f1d79d0f446bc044d04d876
|
|