Skip to content

[main] Update to v1.35.3-k3s1 and Go 1.25.7 #11838

[main] Update to v1.35.3-k3s1 and Go 1.25.7

[main] Update to v1.35.3-k3s1 and Go 1.25.7 #11838

Triggered via pull request March 19, 2026 16:09
Status Failure
Total duration 3m 10s
Artifacts

integration.yaml

on: pull_request
Matrix: Integration Tests
Integration Tests (windows)
0s
Integration Tests (windows)
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
build / Build
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c ./scripts/build" did not complete successfully: exit code: 1
build-windows / Build
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c ./scripts/build" did not complete successfully: exit code: 1
build / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@v3. 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-windows / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@v3. 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/