Merge branch 'master' into deploy #51
mpeDeployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
mpe
approved
|
docker-deploy
and
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
docker-deploy,
and
docker-deploy
|
Annotations
54 errors and 20 warnings
|
build (ppc64le, ubuntu@16.04)
Process completed with exit code 2.
|
|
build (ppc64le, fedora@39)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@42)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@41)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu@18.04)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu@18.04)
Process completed with exit code 2.
|
|
build (ppc64le, korg@13.2.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@14.2.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@33)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@12.3.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@11.3.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@14.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@13.3.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@12.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu@20.04)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@12.4.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu@20.04)
Process completed with exit code 2.
|
|
build (ppc64le, korg@8.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@8.5.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@9.3.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@35)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@35)
The operation was canceled.
|
|
build (ppc64le, ubuntu@22.04)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu@22.04)
The operation was canceled.
|
|
build (ppc64le, fedora@37)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@37)
The operation was canceled.
|
|
build (ppc64le, fedora@34)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, ubuntu)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@34)
The operation was canceled.
|
|
build (ppc64le, ubuntu)
The operation was canceled.
|
|
build (ppc64le, fedora@36)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@36)
The operation was canceled.
|
|
build (ppc64le, fedora)
The operation was canceled.
|
|
build (ppc64le, korg@15.2.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@15.2.0)
The operation was canceled.
|
|
build (ppc64le, fedora@40)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@40)
The operation was canceled.
|
|
build (ppc64le, korg@12.2.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@12.2.0)
The operation was canceled.
|
|
build (ppc64le, fedora@38)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, fedora@38)
The operation was canceled.
|
|
build (ppc64le, korg@11.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@11.1.0)
The operation was canceled.
|
|
build (ppc64le, korg@13.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@13.1.0)
The operation was canceled.
|
|
build (ppc64le, korg@9.4.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@15.1.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@9.4.0)
The operation was canceled.
|
|
build (ppc64le, korg@15.1.0)
The operation was canceled.
|
|
build (ppc64le, korg@5.5.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@5.5.0)
The operation was canceled.
|
|
build (ppc64le, korg@10.3.0)
The strategy configuration was canceled because "build.ppc64le_ubuntu_16_04" failed
|
|
build (ppc64le, korg@10.3.0)
The operation was canceled.
|
|
build (ppc64le, ubuntu@16.04)
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 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/
|
|
build (ppc64le, ubuntu@18.04)
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 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/
|
|
build (ppc64le, ubuntu@20.04)
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 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/
|
|
build (ppc64le, fedora@35)
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 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/
|
|
build (ppc64le, ubuntu@22.04)
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 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/
|
|
build (ppc64le, fedora@37)
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 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/
|
|
build (ppc64le, fedora@34)
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 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/
|
|
build (ppc64le, ubuntu)
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 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/
|
|
build (ppc64le, fedora@36)
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 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/
|
|
build (ppc64le, fedora)
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 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/
|
|
build (ppc64le, korg@15.2.0)
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 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/
|
|
build (ppc64le, fedora@40)
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 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/
|
|
build (ppc64le, korg@12.2.0)
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 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/
|
|
build (ppc64le, fedora@38)
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 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/
|
|
build (ppc64le, korg@11.1.0)
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 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/
|
|
build (ppc64le, korg@13.1.0)
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 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/
|
|
build (ppc64le, korg@9.4.0)
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 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/
|
|
build (ppc64le, korg@15.1.0)
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 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/
|
|
build (ppc64le, korg@5.5.0)
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 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/
|
|
build (ppc64le, korg@10.3.0)
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 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/
|