Skip to content

Bump importmap-rails from 2.0.1 to 2.2.3 #39

Bump importmap-rails from 2.0.1 to 2.2.3

Bump importmap-rails from 2.0.1 to 2.2.3 #39

Triggered via pull request March 24, 2026 13:49
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~GJ3CCN.dockerbuild
58.3 KB
sha256:c41904cc987f28c46a6971732b0e93e5726d0046365d311447e7c7cf39160917
basecamp~writebook~VJ5GZV.dockerbuild
57.3 KB
sha256:23ec2411b6d683e6b837a6f7c5d66f32362363d7d45ea744ab11275c708372a2