Bump github.com/spf13/cobra from 1.6.1 to 1.10.2 #2363
Annotations
12 warnings
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, docker/bake-action@3fc70e1131fee40a422dd8dd0ff22014ae20a1f3, docker/bake-action@6c87dcca988e4e074e3ab1f976a70f63ec9673fb, docker/metadata-action@507c2f2dc502c992ad446e3d7a5dfbe311567a96, docker/setup-buildx-action@f03ac48505955848960e80bbb68046aa35c7b9e7, docker/setup-qemu-action@e81a89b1732b9c48d79cd809d8d81d79c4647a18, step-security/harden-runner@2e205a28d0e1da00c5f53b161f4067b052c61f34. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Post Harden Runner
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>0dhu4aQAAAACbnCz4//sdTLpyUvhjFRx6UEhYMzFFREdFMDUxNwBFZGdl
|
|
Build artifacts:
Dockerfile#L49
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L47
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L21
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "WAYBACK_IPFS_APIKEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Build artifacts:
Dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L9
InvalidBaseImagePlatform: Base image tonistiigi/xx:golang was pulled with platform "linux/amd64", expected "linux/386" for current build
|
|
Build artifacts:
Dockerfile#L48
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L46
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L22
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "WAYBACK_IPFS_SECRET")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Build artifacts:
Dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Build artifacts:
Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
background
wait
wait-all
cancel
Loading