Bump bollard from 0.19.4 to 0.20.2 #6601
Annotations
1 error and 1 warning
|
Build and push to GHCR
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c export AWS_ACCESS_KEY_ID=$(cat /run/secrets/aws_access_key_id) && export AWS_SECRET_ACCESS_KEY=$(cat /run/secrets/aws_secret_access_key) && export AWS_SESSION_TOKEN=$(cat /run/secrets/aws_session_token) && if [ -n \"${SCCACHE_BUCKET:-}\" ]; then export RUSTC_WRAPPER=sccache; fi && cargo build --release --locked --bin lading --features logrotate_fs" did not complete successfully: exit code: 101
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@61815dcd50bd041e203e49132bacad1fd04d2708, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
|
Loading