fix: update golden files for exit codes section + correct 3 wantExitC… #3541
dangrondahlmain.yml
on: push
pre-build
6s
test
/
Lint
38s
test
/
Test
6m 9s
test
/
Snyk Code Test
27s
test
/
Snyk Dependency Test
22s
slack-notification-on-failure
0s
Annotations
3 errors and 6 warnings
|
docker / Docker Build
HTTP 5xx responses were returned as plain fmt.Errorf,\n falling through to exit 1. Now wrapped as ErrServer (exit 2).\n\n3. docs.go/testHelpers/etc: import ordering and alignment (gofmt).",
|
|
docker / Docker Build
per-command exit code sets wired through metaFn; all runnable commands\n get a default set (0/2/3/4), assert commands additionally get 1",
|
|
docker / Docker Build
os.Exit with ExitCodeFor(err) instead of always returning 0\n- assertArtifact: compliance failure now returns ErrCompliance (exit 1)",
|
|
init-kosli / Init Kosli
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: haya14busa/action-cond@v1, kosli-dev/setup-cli-action@v2. 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 / Snyk Dependency Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: kosli-dev/setup-cli-action@v2. 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 / Snyk Code Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: kosli-dev/setup-cli-action@v2. 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 / Lint
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, kosli-dev/setup-cli-action@v2. 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 / Test
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, aws-actions/configure-aws-credentials@v4, codecov/codecov-action@v4, kosli-dev/setup-cli-action@v2. 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/
|
|
docker / Docker Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@36fa7d009e22618ca7cd599486979b8150596c74, actions/attest-sbom/predicate@534423496eab34674190bc45fdacbb8b1198e07f, actions/attest@67422f5511b7ff725f4dbd6fb9bd2cd925c65a8d, actions/setup-go@v5, anchore/sbom-action@v0, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, kosli-dev/setup-cli-action@v2. 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/
|