Skip to content

Merge pull request #3728 from allexistence/docs-clarify-bake-env-over… #6942

Merge pull request #3728 from allexistence/docs-clarify-bake-env-over…

Merge pull request #3728 from allexistence/docs-clarify-bake-env-over… #6942

Triggered via push March 18, 2026 16:22
Status Success
Total duration 16m 8s
Artifacts 116

build.yml

on: push
Matrix: test-integration
Matrix: test-unit
binaries  /  prepare
28s
binaries / prepare
bin-image-prepare
3s
bin-image-prepare
Matrix: binaries / build
bin-image  /  prepare
31s
bin-image / prepare
binaries  /  finalize
51s
binaries / finalize
Matrix: bin-image / build
binaries-finalize
46s
binaries-finalize
bin-image  /  finalize
34s
bin-image / finalize
Fit to window
Zoom out
Zoom in

Annotations

41 warnings
test-unit (ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-unit (macos-15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-unit (windows-2025)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.26.3, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (buildx-stable-1, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (buildx-stable-1, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.25.2, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (master, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.24.0, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.26.3, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (latest, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (master, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (latest, remote, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.24.0, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (master, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (buildx-stable-1, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.25.2, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.26.3, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (master, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (latest, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.25.2, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.24.0, docker-container, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.24.0, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (latest, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.25.2, remote, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (buildx-stable-1, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (v0.26.3, docker-container, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (remote+multinode, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd@28.5, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (remote+multinode, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker@28.5, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker@28.5, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd@28.5, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd@27.5, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker@27.5, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker+containerd@27.5, ./tests, experimental)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test-integration (docker@27.5, ./tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

Artifacts

Produced during runtime
Name Size Digest
buildx
351 MB
sha256:a09b773771ef6b7f7ce82de7ecd6d335468c80eedfc865bcd899f4ac10ee5c3c
docker~buildx~1FCS47.dockerbuild
60 KB
sha256:54908f3d3b2b1e6981c35e95c3271d3189f7dbbdb2ead96e5b30ee8f4daf14bc
docker~buildx~1K7KFY.dockerbuild
119 KB
sha256:6ecc8ef677c0f5196b581b199d4167be2353830a6b89d45d9fa5d3d1cfec8631
docker~buildx~1Z8QR1.dockerbuild
56.8 KB
sha256:68a647138ef6bed0c99cca3a63bfe6fce807f39c1e4c0ec6252d55dcc39d723a
docker~buildx~2GEX3Y.dockerbuild
55.7 KB
sha256:c481d44f53e914e79dd970b37ce292e20378cdc9f9cf05744a2b5994778e843c
docker~buildx~2J3AZD.dockerbuild
56.8 KB
sha256:5a8c965cda24b0ca4359086c2edad8d8636523a55fcc344a29a8961cc707f8c9
docker~buildx~2JDMGF.dockerbuild
116 KB
sha256:8bf967f0dba5b81d611073412d7c4f22eb13ee4b8104b041a2fd026b82f3a338
docker~buildx~2NW8RX.dockerbuild
114 KB
sha256:28df7cc066d25cdf2c553f3972c2cae3c887a6c9578dfbd383700899e6a57abf
docker~buildx~40XAAT.dockerbuild
116 KB
sha256:3e11b5b6462043352db9364f9825d9c652bd57e113593ef7687d342bc988783a
docker~buildx~50D9T5.dockerbuild
62.4 KB
sha256:9a00c4911706f3d106c6c809fbfc75f5fd8d8b20740d185a3cfc3a9ee5fd88b4
docker~buildx~6J5C4N.dockerbuild
116 KB
sha256:fc8b73552d264fe940f1a01b6b66f38a383f149895039479658a1485c806262d
docker~buildx~8BGJC4.dockerbuild
61.7 KB
sha256:9db22b3a73808c5fa22018affe594fd9334cdce0da7016e70c346a3e829b4f3e
docker~buildx~8XGDZ7.dockerbuild
115 KB
sha256:0ab0c73280b127d04df3469f27f472b8cbea5c58594ef0de879c390974c2fa32
docker~buildx~90OXEB.dockerbuild
116 KB
sha256:a4eb4f2f0aa3ffe8daf1e80204495525e2898c299cdbbb1428d65e0ef5d03852
docker~buildx~9D5QIL.dockerbuild
115 KB
sha256:7a35b7fd765d469f1182a41c29d3da4b71021ca1a44d8ec6a72981f4fadfd60a
docker~buildx~9DDFS5.dockerbuild
116 KB
sha256:b024e0d7e45f8ece42ba1e3ba97258bbc93329e72f019abb73ffb2f8815c26dd
docker~buildx~CZAIQJ.dockerbuild
61.3 KB
sha256:04f4e4e5e6d6676c1b8a8c05ab029c4fca00bc46e81c9f53f03bb515d0087f97
docker~buildx~DPMKZ8.dockerbuild
115 KB
sha256:0af6a9fbc35e0f94b0b05b6a6c6cfae4ed7e55db28a5482e36ebe440cbf4166a
docker~buildx~EW0ZMW.dockerbuild
56.9 KB
sha256:373f41d9ebca2f769e6d7d7f60added05f80e959b494cdf7d9acf18b19f1f8b0
docker~buildx~FIHOFZ.dockerbuild
116 KB
sha256:09d6fe3b31efc642098fac20b00f54a0ecc5ae230f9b1b25795ef975d5770c40
docker~buildx~G6IZYF.dockerbuild
116 KB
sha256:fc2bb94b70cb395d881fa8c8811ffb81be7b1104964808a883e0ae67d583b758
docker~buildx~G95NMV.dockerbuild
118 KB
sha256:957ad4f00b9af5fdca2498143beb3ac75b6e8cb0c0550603831d419d6a727064
docker~buildx~I1NRY6.dockerbuild
116 KB
sha256:5b568d8b22c4487a0ea9dec1fcb5394f8aa9e016b122bdb588351a2fff0a50e6
docker~buildx~I3AKWD.dockerbuild
117 KB
sha256:6f5e7c7a159b3805781352634f9752a007892666bbaeec3ff28aac09b019e4f6
docker~buildx~IMWOZ5.dockerbuild
62.5 KB
sha256:bd6c9ab6e695c6d233dd9bcdc65e7a768df50a4aa8cbffb2b82aaeceda8aa937
docker~buildx~IR26BW.dockerbuild
115 KB
sha256:6ddc9f4f6251e370834abe0323b0f75b638494f0d32eb275837a3ea5dc49e6ca
docker~buildx~KS7E71.dockerbuild
56.4 KB
sha256:6e42b84c6f0639663a730e642b1cde2569059190e59f0a6089abcf8ff85d33f2
docker~buildx~L2H23Y.dockerbuild
118 KB
sha256:7a11445596f572bdc57fe969d3c8f24b23cd80cc19ef2a5dfa86da7cd0080f2a
docker~buildx~LEQB38.dockerbuild
56 KB
sha256:8bfb3c4d2274840f778d887c754485c34cdf0c25af73f29f0c865192a2ef97eb
docker~buildx~LMIXE8.dockerbuild
114 KB
sha256:bcb885e9f4c932cb23f51c9f78b134c2f06d4944a63500581fd844c99e7f336e
docker~buildx~LQ51HQ.dockerbuild
62.3 KB
sha256:41190d3e2f5a9509091a7ed5507bcd531d58e4f006364e25709af3ecd028efa2
docker~buildx~N4RQH6.dockerbuild
116 KB
sha256:5e32c92e398b08b1a90cd55fe7c5ea2ce550cef10a6a40fc9f55baa087a0250c
docker~buildx~NNPSLH.dockerbuild
61.5 KB
sha256:ccafee0e2697e4c842e887d81a76f2a03beda268ce0d15ce3a457b2c39451acf
docker~buildx~NQIQFC.dockerbuild
114 KB
sha256:612cc626f4a3669f3329e4c5d72520ddfd2798b7651cff93b84a69e5154a0c88
docker~buildx~NSZ94Z.dockerbuild
56.1 KB
sha256:234e9ea29a341f5ef851117c2946ad29b951b6811567b0438b5eafae49a4a57d
docker~buildx~O4X2DH.dockerbuild
56.8 KB
sha256:7e99d0c4573d6ad560675ee068bbc9839da711c5557740a5906f175ce9a2f701
docker~buildx~OER2LR.dockerbuild
61.2 KB
sha256:e6ecb8114599693fc517dc922b45b71de03515c0a66c30aab9bd64505e526437
docker~buildx~OIUAL4.dockerbuild
118 KB
sha256:4300ac220fe820b92aa9a00a2cefc63e54df4c60c8ed381b51b33f8356174aa2
docker~buildx~OT3LEO.dockerbuild
118 KB
sha256:56d3cca872d787aef97de6957c067e7c74ec41ee0be11f22ea2d73d8fccadfdc
docker~buildx~P3V7GS.dockerbuild
116 KB
sha256:2a0107bcab7ee0ed1163db8c2158a76e2c6ac67ce5ab38802cb4d3580b89cf3a
docker~buildx~P79W11.dockerbuild
117 KB
sha256:f78155d3214157b41a714ce7aa2ed7fe7a8a8f101cd0397f36686e0ffbdfc7be
docker~buildx~PK839U.dockerbuild
55.7 KB
sha256:326dedc6e10a90d0ca8432ae62e5d8627196c5119454468e3f5174c80ec98d01
docker~buildx~PKQSQI.dockerbuild
55.7 KB
sha256:a653e26058a600012a99a0d1a88a9c1dc3eed1c5fc01e46498dffe8a87d54d35
docker~buildx~POOPRE.dockerbuild
55.6 KB
sha256:b00fdebf8dc6db4bfe866197dca93df54b9f305940300a8e4d947b03ceec829f
docker~buildx~QF8XDC.dockerbuild
55.8 KB
sha256:fa1b1e9d6748b78518cf21d2122b5902408c1b287b5f267a3545fb158ebdc977
docker~buildx~QG1O8J.dockerbuild
118 KB
sha256:ef14235dd2d845c279fbe73e5ee3da13546a653e80d1b28fd8aefafaa6d86517
docker~buildx~QWGGSF.dockerbuild
55.4 KB
sha256:1c167effd52982959383e4b764f7fdbc14c6083a774ef6ff91ad6ff87e9bc481
docker~buildx~R04XE0.dockerbuild
61.5 KB
sha256:7e075eedfea4c9606c329027a5bfe6c1ecdfa98aadcf9400385aed49952088bb
docker~buildx~RJXXYI.dockerbuild
56.2 KB
sha256:2d37514177979a82f6c626e42c2c03d7e175e74d8c17959d5744825f17f8994c
docker~buildx~RQTNY2.dockerbuild
61.6 KB
sha256:14993029e471a7a6c26b5a4c7796855b659844968647039cb7eaef682578198a
docker~buildx~RYFEBI.dockerbuild
116 KB
sha256:ad8f5f06e4a4805ed5e65b23a6326b401e4d9d278fbf60068f98a381f214c88c
docker~buildx~S66APU.dockerbuild
116 KB
sha256:9f84a5e56f1a51cde22b4c63d703f20e63738741623e699d31edc9ae5a8be2dc
docker~buildx~SACTL6.dockerbuild
56.6 KB
sha256:c9df6688473c92cfb315240c72b2b50e012d6090ef169d54f8a5280584a2ecd5
docker~buildx~TGSU3J.dockerbuild
115 KB
sha256:97df155c0d6867f449d675053e8bbe5a4f8d036311d14ccaf2d360fb473589de
docker~buildx~THT689.dockerbuild
115 KB
sha256:9dcb453469a36fa41cdc4eb5b310edf29f134d4f5ffa864946decc5783ff4568
docker~buildx~TN2SFG.dockerbuild
62.2 KB
sha256:3aed339dda171511de48732951aed253c92f986d96ebb99fb6a7a3ccd87d379e
docker~buildx~TP6LYN.dockerbuild
117 KB
sha256:89317fd4f68292e28c5a3fc1ed1f3763f16d90e4247c45674e98f14621a06019
docker~buildx~UEQZ7R.dockerbuild
116 KB
sha256:b311a0592675a9abf95863e6a7090956eb4826bcec98de1f3c487c334419cb4c
docker~buildx~UJ3365.dockerbuild
114 KB
sha256:79adf51ba9de1a6f087b64f7ef69f7c4a4f89072f6896f123144c42cb685bfde
docker~buildx~URCNUR.dockerbuild
62.1 KB
sha256:03342f1ba23b83e1e5e36e3243bab835d3d6a811116a83c51d16375cb527c194
docker~buildx~V97KLQ.dockerbuild
60.8 KB
sha256:26f8c811bfc8ebda41ef0d447eefa8b478a9f2fdf3258e7a3eb000fe6c0ebf56
docker~buildx~VMVCHX.dockerbuild
117 KB
sha256:36efabaa88048efbde7475c7b2d133a5592731787e922330467a64f3a4c3c51c
docker~buildx~W0NGW8.dockerbuild
62.6 KB
sha256:d71993da3e5a8ddf492aafff3f5b1f4e29fbab98231a7de1555154f26dc0778e
docker~buildx~W4RD9L.dockerbuild
55.1 KB
sha256:3ffec7f08cd20d1cdb34357782f091eab3c326673faecda73d68ea82bd4c5eba
docker~buildx~W8T3F2.dockerbuild
114 KB
sha256:fe96d5c75e2fb5a61048e72a00801fdb0778c7c6e03a849be8972275cce67b2e
docker~buildx~WFO8F7.dockerbuild
61.1 KB
sha256:5d2099a9bc4d6e53ced9bb0a683234d77363f44bb14bbb2ea5d56e197e317c00
docker~buildx~WI8MCF.dockerbuild
117 KB
sha256:4daf24423be9ae8af4a44355eb1b50df379fd5d65a74f84dc168d024b401b6e9
docker~buildx~XGK8HB.dockerbuild
117 KB
sha256:724bcc79171fcd6a4ecac5c5444544925f1d7f96d4e2f78ec3ed683594132703
docker~buildx~XN80EV.dockerbuild
55.8 KB
sha256:d42da5613fa5a98154fb1061fb36ecea73624d38cba82f1619948e09aa5fb9cc
docker~buildx~XNM3HM.dockerbuild
54.7 KB
sha256:20c145c2f59023062a1f6577bbbf7627166aba2f50ae8b885a5707f62980ba19
docker~buildx~XQ1JL9.dockerbuild
61.6 KB
sha256:5ffba8fcc6e34caf18fe0ff3fbca96626402458d1bfad5d4bed445c4ebf483d7
docker~buildx~YDKM5H.dockerbuild
61.1 KB
sha256:d525aee3c73e9c91a12562af2b32aa9201b34ca2629b4a7aba5d83c2b9b02423
docker~buildx~YFBM52.dockerbuild
118 KB
sha256:daf210d30a7963ee2fc0e738b3068bdf9bb074affb44ba6d79938b76dcd4ad35
docker~buildx~YJD45N.dockerbuild
116 KB
sha256:c90b13b8ce7726375aff7a7aa94b5f5c678ca4763ddc03efab239b9f3e50f297
release
350 MB
sha256:b1bcb1900575d0fc1ad6af56ba58f1f2bb2d08d4438d2b91508dad5c8dc358f1
test-reports-test-integration-tests--docker-
145 KB
sha256:7d327a0a4a4a5608f9224b1a407188b9ada803fda78e7537c88a4408c69eeb16
test-reports-test-integration-tests--docker-experimental
157 KB
sha256:c9ac8de5d29a4fa4ffdbd0db19b5d07e45d2b122314691097c0fefc70190db8b
test-reports-test-integration-tests--docker275-
140 KB
sha256:4a82ffa9de56533f62ce9d336f3da7c9eef3da48021a5969c249c4d42e39e5ca
test-reports-test-integration-tests--docker275-experimental
152 KB
sha256:07c3ce68ad8a98291218e7343ecdf9f8354f782afdd9bd2ab50642378e89f322
test-reports-test-integration-tests--docker285-
140 KB
sha256:df672a2a8db6c631acc9376cc06ab6225d4efcd1059d587cd3f1b61f285f0f68
test-reports-test-integration-tests--docker285-experimental
152 KB
sha256:9a2d9397791dd45a15dff3a0dd6a89eccdb3758d4a80eef83ee79a47a3cfb8e2
test-reports-test-integration-tests--dockercontainerd-
145 KB
sha256:bc0edefbd921b8cc59e674650db2a60ac53d5c8e73902d83c79c3042f53e2c63
test-reports-test-integration-tests--dockercontainerd-experimental
157 KB
sha256:4750bafeff025db24ff4b65803883e846f11f27de89d5ecf9643d233c2a4e090
test-reports-test-integration-tests--dockercontainerd275-
141 KB
sha256:9481bac9e6d21a803058ca3303ca5ed5a7e9dff4447130507dc996253a7d2e84
test-reports-test-integration-tests--dockercontainerd275-experimental
152 KB
sha256:f5d4000f7bf7eafda11af6d191bf3e8a2413592a8a35d1cd36532207f3ff3e8c
test-reports-test-integration-tests--dockercontainerd285-
141 KB
sha256:cce34b4c669b42bf9de1bb13fc80143b80d5a771e8a108517c08d939254d87f8
test-reports-test-integration-tests--dockercontainerd285-experimental
152 KB
sha256:3e1b8142a763503c6bf48799a9008c19b9e3ceedb952dea996f79d8424db455a
test-reports-test-integration-tests--remotemultinode-
144 KB
sha256:905c352983bda5c061a519fb6c8910e32828e26f9897f7f410e9d6229cae333e
test-reports-test-integration-tests--remotemultinode-experimental
155 KB
sha256:17cdf343faff0f93e7a9fb67fcbff00604a7d3b12ef13e822e826b72ead7e385
test-reports-test-integration-tests-buildx-stable-1-docker-container-
145 KB
sha256:681e64cddd7dc6548ced30ec5e3847b3956cf8dacc81f0958caf5cc69bc740b9
test-reports-test-integration-tests-buildx-stable-1-docker-container-experimental
158 KB
sha256:86ac1c410755d00547838364c777e32cf0d22066d5fee340d3ab36b83e613e70
test-reports-test-integration-tests-buildx-stable-1-remote-
145 KB
sha256:bd06bb67e1bde2f04b179c9a0158548027118df72dae888dba75c5759db7c097
test-reports-test-integration-tests-buildx-stable-1-remote-experimental
157 KB
sha256:5af60ec4f64f30bb8fa419b1e95302b18371f560b237cc2c259170b1c34adc4b
test-reports-test-integration-tests-latest-docker-container-
145 KB
sha256:aa545858ed5d5a5822f6c158247421bc7a5c0c769fd2dabaf67f9ae04f1a48ee
test-reports-test-integration-tests-latest-docker-container-experimental
157 KB
sha256:3d00469369d55f84423cbef565a3cf57364d7838e2db1619c5ecfece32bce118
test-reports-test-integration-tests-latest-remote-
145 KB
sha256:24c7b225a573fbae1b8dc7d5b0481a1cd226e07b94f54d55f1df2abf2bbcf9de
test-reports-test-integration-tests-latest-remote-experimental
157 KB
sha256:e771a6239cbd4d9ef5246febba35298e4722091f508da92c69e457ab113b6381
test-reports-test-integration-tests-master-docker-container-
145 KB
sha256:6d687a6c229005691ff64ff4e4d5cdae820e6b0a179cc3e48db6bd2116aab96c
test-reports-test-integration-tests-master-docker-container-experimental
158 KB
sha256:a08afb388a9bf2a102c1568fce0dafeb5fddece058ae33e66520ec83cd8d6933
test-reports-test-integration-tests-master-remote-
144 KB
sha256:6526fd83db23376f1db848e015d1925868362ea6f335265f48c3c6afd55b1cc7
test-reports-test-integration-tests-master-remote-experimental
156 KB
sha256:8221ac326eae31cf780a8a0adbc9bdbe27e1720e08c5bfe7ff7cb850d85fe1e3
test-reports-test-integration-tests-v0240-docker-container-
140 KB
sha256:6313b5d25bee215c83dd95cf493094524d12787b3f769bdfeda08d1a07409cc9
test-reports-test-integration-tests-v0240-docker-container-experimental
153 KB
sha256:5a9de8f90963d9e0950715e45a20297c347369efb3f01d8e0d1f3deb11ff0a94
test-reports-test-integration-tests-v0240-remote-
140 KB
sha256:97d704ef619031fb0a9e40b9216530f9e8081c1fe901166db11540fa80d214a5
test-reports-test-integration-tests-v0240-remote-experimental
153 KB
sha256:5602ce9d094830eca3fe76871f55c777719398e889eb0345fd62f0ff1bcaec05
test-reports-test-integration-tests-v0252-docker-container-
140 KB
sha256:79dbbeec660b9c76f03f026dccd80a2cbb1839c1cf8c2341236ed535b0a5923b
test-reports-test-integration-tests-v0252-docker-container-experimental
152 KB
sha256:48c0dfa8093cef330f5a823b85b41ef6d5a5b073dead27f942e7a87dffe718b9
test-reports-test-integration-tests-v0252-remote-
140 KB
sha256:ff1cab90bc65b68cdbe921ede38d2b828459086ba1ab528fe08988156e615178
test-reports-test-integration-tests-v0252-remote-experimental
154 KB
sha256:6723301808dff8212ebd8a9377515655696971b2dabf5403f25d8a4c7f84b8ef
test-reports-test-integration-tests-v0263-docker-container-
145 KB
sha256:476d501f49517ebc1e2fceebc8d7a963c83852e721ff7a56954fb833ec662c5f
test-reports-test-integration-tests-v0263-docker-container-experimental
158 KB
sha256:c6cd6935f76f22b123ede512a9fd0b43c300372632e689095f170cdc14f892c7
test-reports-test-integration-tests-v0263-remote-
144 KB
sha256:e5fd1c5efbc2bb095215b6045f6e5fcf3b9dc18ab31a8aca1fdb997e5a6a0299
test-reports-test-integration-tests-v0263-remote-experimental
157 KB
sha256:7b52955cce4223b89dbf58cb03974ae197ddf743d07c551176f415298c1861f0
test-reports-test-unit--macos-15
253 KB
sha256:24c5ca51d8d0dcc3d3cc816815149818c7d0742fba6a41cd7701ceff44eb2b2c
test-reports-test-unit--ubuntu-24.04
283 KB
sha256:e848d720f86187b93b2495d43318294fc510f714dfae6347efedc18750455f79
test-reports-test-unit--windows-2025
219 KB
sha256:faf4133bb0ec161d65df8e8d2277c3393357b8a26a36965faff2c94ab3b47b0e