Add supported version for Mage-OS 2.2.1 #173
Triggered via pull request
March 18, 2026 15:02
Status
Failure
Total duration
1d 0h 0m 12s
Artifacts
–
_internal-integration.yaml
on: pull_request
compute_matrix
4s
Matrix: integration-workflow / integration_test
Annotations
73 errors and 90 warnings
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p7)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p7)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p6)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p6)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p2)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p2)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p5)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p5)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p13)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p13)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p2)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p2)
Failed to initialize container elasticsearch:7.16.3
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p10)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p10)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4)
Failed to initialize container elasticsearch:7.16.3
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p12)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p12)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p4)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p4)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p12)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p12)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p11)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p11)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p3)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p3)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p5)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p5)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p6)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p6)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p1)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p1)
Failed to initialize container elasticsearch:7.16.3
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p9)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p9)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p1)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p1)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p3)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p3)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p8)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p8)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p9)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p9)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p14)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p14)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p7)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p7)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p8)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p8)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p4)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p4)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p11)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p11)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p13)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p13)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p10)
One or more containers failed to start.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p10)
Failed to initialize container elasticsearch:7.17.5
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.2-p1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.1-p1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.0-p1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.3-p3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.3.7-p4)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.0)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.3-p2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.2-p2)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.3.7-p3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.3-p1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.1)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.3)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
compute_matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./supported-version, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p7)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p6)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p2)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p5)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p13)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p2)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p10)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p12)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p4)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p12)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p11)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p3)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p5)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p6)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p1)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p6)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p8)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.8-p2)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p10)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p3)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p1)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p9)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p1)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p1)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.8)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p3)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p5)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p8)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p4)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p9)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p2)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p8)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p14)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p6)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.8-p3)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p7)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p7)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p5)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p8)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p4)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p2)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p4)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p14)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.5-p11)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p13)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.4-p10)
No files were found with the provided path: /home/runner/work/infrastructure/magento2/dev/tests/integration/tmp/sandbox-*. No artifacts will be uploaded.
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p7)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p11)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.7-p9)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p9)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p3)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p13)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.6-p12)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.8-p1)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
integration-workflow / integration_test (magento/project-community-edition:2.4.8-p4)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|