Skip to content
CI

fix(ci): use PAT in release-please to trigger goreleaser #4

Sign in to view logs

fix(ci): use PAT in release-please to trigger goreleaser

fix(ci): use PAT in release-please to trigger goreleaser #4

Triggered via pull request March 13, 2026 08:48
@eskpeskp
opened #3
feature/distribution-pipeline
Status Failure
Total duration 2m 25s
Artifacts –

ci.yml

on: pull_request
lint
17s
lint
test
2m 22s
test
docs-check
15s
docs-check
integration-test
0s
integration-test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
docs-check
Process completed with exit code 128.
lint
Command failed: /home/runner/golangci-lint-2.11.3-linux-amd64/golangci-lint config verify jsonschema: "issues" does not validate with "/properties/issues/additionalProperties": additional properties 'exclude-rules' 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.11.3-linux-amd64/golangci-lint config verify jsonschema: "issues" does not validate with "/properties/issues/additionalProperties": additional properties 'exclude-rules' not allowed The command is terminated due to an error: the configuration contains invalid elements , Error: Command failed: /home/runner/golangci-lint-2.11.3-linux-amd64/golangci-lint config verify jsonschema: "issues" does not validate with "/properties/issues/additionalProperties": additional properties 'exclude-rules' 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)
docs-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. 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/