Skip to content

AI Supply Chain Feature #750

AI Supply Chain Feature

AI Supply Chain Feature #750

Triggered via pull request April 6, 2026 09:05
Status Failure
Total duration 2h 6m 20s
Artifacts

ci-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 22 warnings
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls client.Client.ImageSave
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls client.Client.ImagePull
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls client.Client.ImageInspectWithRaw
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls client.Client.ImageInspect
govulncheck
wrappers.ContainerResolverImpl.Resolve calls containerResolver.ContainersResolver.Resolve, which eventually calls client.Client.Close
govulncheck
wrappers.request calls http.Client.Do, which eventually calls client.CheckRedirect
govulncheck
wrappers.init calls containerResolver.init, which eventually calls checkpoint.init
govulncheck
wrappers.init calls containerResolver.init, which eventually calls build.init
govulncheck
wrappers.init calls containerResolver.init, which eventually calls blkiodev.init
govulncheck
wrappers.init calls containerResolver.init, which eventually calls api.init
lint
issues found
lint: internal/commands/scan_test.go#L844
string `sast,kics,sca,aisc` has 4 occurrences, make it a constant (goconst)
scan Docker Image with Trivy
Process completed with exit code 1.
integration-tests
Process completed with exit code ***.
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v4.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 save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>013fTaQAAAACHV2N3s6gUTqcQnmeR4lmNUEFPRURHRTA1MjAARWRnZQ==
govulncheck
Failed to restore: Cache service responded with 400
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
lint
Unexpected input(s) 'skip-pkg-cache', valid inputs are ['version', 'version-file', 'install-mode', 'install-only', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'args', 'skip-cache', 'skip-save-cache', 'cache-invalidation-interval', 'problem-matchers', 'debug', 'experimental']
lint
Failed to restore: Cache service responded with 400
scan Docker Image with Trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@722adc63f1aa60a57ec37892e133b1d319cae598, docker/login-action@49ed152c8eca782a232dede0303416e8f356c37b, docker/setup-buildx-action@cf09c5c41b299b55c366aff30022701412eb6ab0. 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/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
scan Docker Image with Trivy
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
unit-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@1e31de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c2316fe8122ab82dc22947d607c0c91f9. 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/
unit-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0BoDTaQAAAABp3NpK7bV4SLbSRcmvAtFzUEhMMzBFREdFMDQxNABFZGdl
unit-tests
Failed to restore: Cache service responded with 400
integration-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@***e3***de5234b9f8995739874a8ce0492dc87873e2, actions/setup-go@4d34df0c23***6fe8***22ab82dc22947d607c0c9***f9. 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 ***6th, 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-***9-deprecation-of-node-20-on-github-actions-runners/
integration-tests
Failed to restore: Cache service responded with 400