fix(deps): update module github.com/onsi/ginkgo/v2 to v2.28.3 #1778
gardener-ci-robotnon-release.yaml
on: push
build
/
...
/
version-and-ocm
34s
Matrix: build / test
build
/
...
/
run-linter
7m 24s
Matrix: build / Build OCI-Images
Matrix: build / Build Helmcharts
component-descriptor
/
component-descriptor
24s
component-descriptor
/
repo-metadata
3s
component-descriptor
/
...
/
Create Draft-Release
16s
Annotations
10 warnings
|
build / Build OCI-Images (tm-base-image, base-step, testmachinery/base-step) / build-images (linux/amd64, ubuntu-latest, 0.323.0-5c86d60c348639df3c274a23ca82129210ae2a37-linux_...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / test (.ci/test-definitions)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-kubectl@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build OCI-Images (tm-controller, tm-controller, testmachinery/testmachinery-controller) / build-images (linux/amd64, ubuntu-latest, 0.323.0-5c86d60c348639df3c274a23ca82129210ae2a37-linux_...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build OCI-Images (tm-bot, tm-bot, testmachinery/bot) / build-images (linux/amd64, ubuntu-latest, 0.323.0-5c86d60c348639df3c274a23ca82129210ae2a37-linux_...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build OCI-Images (tm-run, tm-run, testmachinery/testmachinery-run) / build-images (linux/amd64, ubuntu-latest, 0.323.0-5c86d60c348639df3c274a23ca82129210ae2a37-linux_...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build OCI-Images (tm-prepare-image, tm-prepare, testmachinery/prepare-step) / build-images (linux/amd64, ubuntu-latest, 0.323.0-5c86d60c348639df3c274a23ca82129210ae2a37-linux_...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / test (.ci/test)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-kubectl@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build Helmcharts (testmachinery, charts/testmachinery, testmachinery/charts, ocm-resource:argo-wo... / helmchart
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / Build Helmcharts (testmachinery-bot, charts/tm-bot, testmachinery/charts, ocm-resource:tm-bot.rep... / helmchart
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / sast-lint / run-linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
484fea6e00f8f64d8b04e3879a3a13ceb0484374.ocm-artefacts
|
1.13 KB |
sha256:4225c495a1d942c7005d95f46a020c66031023b347b5929401613a113dd638e7
|
|
|
4ff2a21cb8164483a75ba4d173415b3ef4bf70a5.ocm-artefacts
|
613 Bytes |
sha256:7b1bff97a955865f1f6be465157850225a0862dde3a756817e384f5ffb3004e9
|
|
|
7d68d13d9bdda017fe66ea426a47d3bbee9b8f8f.ocm-artefacts
|
1000 Bytes |
sha256:0a400505d06301544fb807dd6aac4005d54cd26a06659293ef0187d830d5fadf
|
|
|
a56bf131b4b91f35b96908831674238642071f9f.ocm-artefacts
|
609 Bytes |
sha256:176506309df5ce3f1e5126ed9b1d0d26f4d3b6da47af2ef2939776dbd8c66aaf
|
|
|
ab261f633a3a7388f507e7a5901a4160030b2b01.ocm-artefacts
|
608 Bytes |
sha256:8cfe50105be1b8c537eff4f058c60de744e007ccba990daabe18b788d3ebb371
|
|
|
base-component-descriptor
|
1.14 KB |
sha256:ee1d2743b22c58cd690b48fb26c86866df19dd9f82b0f9f70f293833dbcfdb31
|
|
|
c9637a66cc58ca5579442a5c39e2a0f6b0b3209e.ocm-artefacts
|
4.42 KB |
sha256:702c5324c66eb2a8afa67e2216ae519b2b4bd678fc7471f30c1f43850a096810
|
|
|
component-descriptor
|
1.14 KB |
sha256:8799565c3faf7f801492d946ba6db9b6e182fa2d1f1f8673bec07e41a09d163f
|
|
|
d80546112f4d8da9db71dd80eacd27c6d0248004.ocm-artefacts
|
606 Bytes |
sha256:36b61172216206c35dd5c5f47e69ecbd41393420745f852df22576f07634cc56
|
|
|
eb0316c9e00405e76635ed34d9dd90d9575406f0.ocm-artefacts
|
612 Bytes |
sha256:d80586fb437bc3b1f6fd7eaf6f9db897af0d9c5b7ebceb21016722435ae3254b
|
|
|
gardener~test-infra~JTTLQ6.dockerbuild
|
37.1 KB |
sha256:abf2759bb9694a141406fb8eaf66fa1ff53c27ccc887d2f358a3dd934e31b07f
|
|
|
gardener~test-infra~O087NQ.dockerbuild
|
36.4 KB |
sha256:76e4e4c9aea2856d08579a70a2d1597934fe43973f87f6b03c2bba7cb815c900
|
|
|
gardener~test-infra~O9XNI3.dockerbuild
|
40.1 KB |
sha256:00a7396a31a810ba351284ee6a595eeb2caeeb1a8cb404c0d4dbdd1fb5b696cf
|
|
|
gardener~test-infra~T3ZK3H.dockerbuild
|
39.8 KB |
sha256:802134bf63b1894cb27ec2c0e85462b07524d746896151f445e9001107bb6048
|
|
|
gardener~test-infra~TV47MS.dockerbuild
|
26.7 KB |
sha256:4160cba0fb5ac454d02f80a14d6e51291013257b19a10532ab9e0e71312826ec
|
|
|
prepare-workflow-values
|
1.16 KB |
sha256:e2dfbce66b09db4898b77549b415759063c67c11b62862c3df80d5e2026df758
|
|
|
release-commit-objects
|
1.7 KB |
sha256:7211540a3acc61a97ba436a4d5fd36a8dc057bbe4afd7648665d63f88544c723
|
|