Skip to content

feat: configurator landing page, inline editor flow, CI improvements #2

feat: configurator landing page, inline editor flow, CI improvements

feat: configurator landing page, inline editor flow, CI improvements #2

Triggered via pull request April 15, 2026 13:36
Status Failure
Total duration 39s
Artifacts

e2e.yml

on: pull_request
Deploy single-account stack
12s
Deploy single-account stack
Deploy multi-account StackSet
12s
Deploy multi-account StackSet
Create networking resources
Create networking resources
Create core compute resources
Create core compute resources
Create analytics resources
0s
Create analytics resources
Create integration resources
Create integration resources
Create security resources
Create security resources
Create devtools resources
Create devtools resources
Create ML/AI resources
Create ML/AI resources
Create media and IoT resources
Create media and IoT resources
Create miscellaneous resources
Create miscellaneous resources
Create global us-east-1 resources
0s
Create global us-east-1 resources
Create global us-west-2 resources
Create global us-west-2 resources
Create resources in linked account 1
0s
Create resources in linked account 1
Create resources in linked account 2
0s
Create resources in linked account 2
Create resources in linked account 3
0s
Create resources in linked account 3
Create resources in linked account 4
0s
Create resources in linked account 4
Create resources in linked account 5
0s
Create resources in linked account 5
Create database resources
Create database resources
Verify map-migrated tags
Verify map-migrated tags
Teardown all E2E resources
18s
Teardown all E2E resources
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Deploy multi-account StackSet
Process completed with exit code 1.
Deploy single-account stack
Process completed with exit code 255.
Deploy multi-account StackSet
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-python@v5, aws-actions/configure-aws-credentials@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/
Deploy single-account stack
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-python@v5, aws-actions/configure-aws-credentials@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/
Teardown all E2E resources
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-python@v5, aws-actions/configure-aws-credentials@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/