Skip to content

[v2 of 169] feat: issue-169 (rescue from deleted branch) #173

[v2 of 169] feat: issue-169 (rescue from deleted branch)

[v2 of 169] feat: issue-169 (rescue from deleted branch) #173

Triggered via pull request June 16, 2026 15:00
Status Failure
Total duration 2m 21s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 7 warnings
golangci-lint
issues found
golangci-lint: cmd/sin-code/spec_cmd.go#L226
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/wiring/spec.go#L72
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/spec/pr4_test.go#L170
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/spec/json.go#L3
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/spec/drift.go#L39
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/spec/check.go#L23
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/spec/author.go#L28
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/learning/coverage_test.go#L85
File is not properly formatted (gofmt)
golangci-lint: cmd/sin-code/internal/hooklife/coverage_test.go#L23
File is not properly formatted (gofmt)
govulncheck
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 16th, 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/
govulncheck
The process '/usr/bin/git' failed with exit code 128
golangci-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, golangci/golangci-lint-action@v8. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
golangci-lint
The process '/usr/bin/git' failed with exit code 128
gosec (SARIF upload)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/upload-sarif@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
gosec (SARIF upload)
The process '/usr/bin/git' failed with exit code 128
gosec (SARIF upload)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/