Skip to content

chore: update golangci-lint action to v9 and pin version #7

chore: update golangci-lint action to v9 and pin version

chore: update golangci-lint action to v9 and pin version #7

Triggered via push March 19, 2026 13:51
Status Failure
Total duration 2m 3s
Artifacts

ci.yml

on: push
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
lint
Command failed: /home/runner/golangci-lint-2.10.1-linux-amd64/golangci-lint config verify jsonschema: "version" does not validate with "/properties/version/type": got number, want string jsonschema: "linters" does not validate with "/properties/linters/additionalProperties": additional properties 'fast' not allowed jsonschema: "" does not validate with "/additionalProperties": additional properties 'linters-settings' not allowed The command is terminated due to an error: the configuration contains invalid elements
lint
Failed to run: Error: Command failed: /home/runner/golangci-lint-2.10.1-linux-amd64/golangci-lint config verify jsonschema: "version" does not validate with "/properties/version/type": got number, want string jsonschema: "linters" does not validate with "/properties/linters/additionalProperties": additional properties 'fast' not allowed jsonschema: "" does not validate with "/additionalProperties": additional properties 'linters-settings' not allowed The command is terminated due to an error: the configuration contains invalid elements , Error: Command failed: /home/runner/golangci-lint-2.10.1-linux-amd64/golangci-lint config verify jsonschema: "version" does not validate with "/properties/version/type": got number, want string jsonschema: "linters" does not validate with "/properties/linters/additionalProperties": additional properties 'fast' not allowed jsonschema: "" does not validate with "/additionalProperties": additional properties 'linters-settings' not allowed The command is terminated due to an error: the configuration contains invalid elements at genericNodeError (node:internal/errors:985:15) at wrappedFn (node:internal/errors:539:14) at ChildProcess.exithandler (node:child_process:417:12) at ChildProcess.emit (node:events:508:28) at maybeClose (node:internal/child_process:1101:16) at ChildProcess._handle.onexit (node:internal/child_process:305:5)
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/
check-codebase
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/
ci - ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/
ci - windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/