Skip to content

Merge branch 'fix-reset-fields-node-pool-update' into 'crusoe-cluster… #310

Merge branch 'fix-reset-fields-node-pool-update' into 'crusoe-cluster…

Merge branch 'fix-reset-fields-node-pool-update' into 'crusoe-cluster… #310

Triggered via push April 30, 2026 07:17
Status Failure
Total duration 2m 41s
Artifacts

verify.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
verify
Process completed with exit code 1.
verify: cluster-autoscaler/cloudprovider/crusoecloud/crusoe_node_group.go#L528
should omit 2nd value from range; this loop is equivalent to `for i := range ...`
verify: cluster-autoscaler/cloudprovider/crusoecloud/crusoe_manager.go#L488
receiver name m should be consistent with previous receiver name mgr for crusoeManager
verify: cluster-autoscaler/cloudprovider/crusoecloud/crusoe_manager.go#L467
receiver name m should be consistent with previous receiver name mgr for crusoeManager
verify: cluster-autoscaler/cloudprovider/crusoecloud/crusoe_manager.go#L364
receiver name m should be consistent with previous receiver name mgr for crusoeManager
verify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/setup-go@v5.5.0. 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/