Skip to content
This repository has been archived by the owner on Nov 28, 2024. It is now read-only.

build(deps): bump the go group across 1 directory with 20 updates #445

build(deps): bump the go group across 1 directory with 20 updates

build(deps): bump the go group across 1 directory with 20 updates #445

Triggered via pull request June 2, 2024 19:31
Status Failure
Total duration 3m 19s
Artifacts

tests.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test-linux: main.go#L37
could not import github.com/open-component-model/mpas-product-controller/controllers (-: # github.com/open-component-model/mpas-product-controller/controllers
test-linux: controllers/productdeployment_controller.go#L337
unknown field References in struct literal of type "github.com/open-component-model/ocm-controller/api/v1alpha1".ComponentVersionSpec
test-linux: controllers/productdeployment_controller.go#L337
undefined: ocmv1alpha1.ReferencesConfig
test-linux: controllers/productdeploymentpipeline_scheduler.go#L113
cannot use eventv1.EventSeverityError (constant "error" of type string) as map[string]string value in argument to event.New
test-linux: controllers/productdeploymentpipeline_scheduler.go#L113
cannot use nil as string value in argument to event.New
test-linux: controllers/productdeploymentpipeline_scheduler.go#L126
cannot use eventv1.EventSeverityError (constant "error" of type string) as map[string]string value in argument to event.New
test-linux: controllers/productdeploymentpipeline_scheduler.go#L126
cannot use nil as string value in argument to event.New
test-linux: controllers/productdeploymentpipeline_scheduler.go#L132
cannot use eventv1.EventSeverityInfo (constant "info" of type string) as map[string]string value in argument to event.New
test-linux: controllers/productdeploymentpipeline_scheduler.go#L132
cannot use nil as string value in argument to event.New) (typecheck)
test-linux
Process completed with exit code 2.
test-linux
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.