Skip to content

Allow instrumentation versions to be marked as unupgradable #13613

Allow instrumentation versions to be marked as unupgradable

Allow instrumentation versions to be marked as unupgradable #13613

Triggered via pull request April 15, 2026 16:18
Status Failure
Total duration 17m 11s
Artifacts

continuous-integration.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
Govulncheck
config.init calls install.init, which eventually calls client.init
Govulncheck
config.LoadFromCLI calls errors.As, which eventually calls client.httpError.Unwrap
Govulncheck
sidecar.sidecarPodMutator.Mutate calls errors.Is, which eventually calls client.httpError.Is
Govulncheck
hack.main calls client.httpError.Error
Govulncheck
config.LoadFromCLI calls errors.As, which eventually calls client.errConnectionFailed.Unwrap
Govulncheck
hack.main calls client.errConnectionFailed.Error
Govulncheck
config.init calls install.init, which eventually calls checkpoint.init
Govulncheck
config.init calls install.init, which eventually calls build.init
Govulncheck
config.init calls install.init, which eventually calls blkiodev.init
Govulncheck
config.init calls install.init, which eventually calls api.init
Govulncheck
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.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/
Govulncheck
Failed to restore: Cache service responded with 400
Security
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.