Skip to content

Bump bcrypt from 3.1.20 to 3.1.21 #33

Bump bcrypt from 3.1.20 to 3.1.21

Bump bcrypt from 3.1.20 to 3.1.21 #33

Triggered via pull request March 20, 2026 15:36
Status Success
Total duration 2m 32s
Artifacts 2

publish-image.yml

on: pull_request
Matrix: build
Create multi-arch manifest and sign
0s
Create multi-arch manifest and sign
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Build and push image (arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1, docker/metadata-action@c1e51972afc2121e065aed6d45c65596fe445f3f, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior: Dockerfile#L18
RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Build and push image (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@184bdaa0721073962dff0199f1fb9940f07167d1, docker/metadata-action@c1e51972afc2121e065aed6d45c65596fe445f3f, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior: Dockerfile#L18
RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Artifacts

Produced during runtime
Name Size Digest
basecamp~writebook~JZQFUU.dockerbuild
57.5 KB
sha256:4282697559ce7b45fb90a54deef91eb564fdd444101eb134ce51498daaa84d2d
basecamp~writebook~USARIR.dockerbuild
57.1 KB
sha256:5bf7006d961d5498d0724afd5ddcfe45d6cc91c3bdaf817d475673fff80a83a4