Skip to content

govulncheck

govulncheck #886

Triggered via schedule April 8, 2026 05:20
Status Failure
Total duration 40s
Artifacts

govulncheck.yml

on: schedule
Run govulncheck
38s
Run govulncheck
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 warnings
Run govulncheck
Process completed with exit code 3.
Run govulncheck
csaf.compiledSchema.validate calls sync.Once.Do, which eventually calls bbolt.Tx.Rollback
Run govulncheck
csaf.prepareCache calls bbolt.Open
Run govulncheck
csaf.boltCache.get calls bbolt.DB.View
Run govulncheck
csaf.prepareCache calls bbolt.DB.Update
Run govulncheck
csaf.remoteValidator.Close calls bbolt.DB.Close
Run govulncheck
csaf.compiledSchema.validate calls sync.Once.Do, which eventually calls bbolt.Bucket.Stats
Run govulncheck
csaf.compiledSchema.validate calls sync.Once.Do, which eventually calls bbolt.Bucket.ForEachBucket
Run 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.1.1, actions/setup-go@v5.0.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/
Run govulncheck
Failed to restore: Cache service responded with 400
Run govulncheck
Both go-version and go-version-file inputs are specified, only go-version will be used