Bump the gomod group with 2 updates #389
Annotations
5 errors and 2 warnings
|
unit-test (1.26.4)
Process completed with exit code 1.
|
|
unit-test (1.26.4):
pkg/attest/sign.go#L20
cannot use bundle (variable of interface type signer.SignedArtifact) as "google.golang.org/protobuf/proto".Message value in argument to protojson.Marshal: signer.SignedArtifact does not implement protoreflect.ProtoMessage (missing method ProtoReflect)
|
|
unit-test (1.25.11)
The strategy configuration was canceled because "unit-test._1_26_4" failed
|
|
unit-test (1.25.11)
The operation was canceled.
|
|
unit-test (1.25.11):
pkg/attest/sign.go#L20
cannot use bundle (variable of interface type signer.SignedArtifact) as "google.golang.org/protobuf/proto".Message value in argument to protojson.Marshal: signer.SignedArtifact does not implement protoreflect.ProtoMessage (missing method ProtoReflect)
|
|
verify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-protoc@c65c819552d16ad3c9b72d9dfd5ba5237b9c906b, bufbuild/buf-setup-action@a47c93e0b1648d5651a065437926377d060baa99. 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/
|
|
verify
No github_token supplied, API requests will be subject to stricter rate limiting
|