Skip to content
Build and publish container image to GHCR

Merge pull request #392 from basecamp/sanitize-edit-history-xss #11

Sign in to view logs

Merge pull request #392 from basecamp/sanitize-edit-history-xss

Merge pull request #392 from basecamp/sanitize-edit-history-xss #11

Triggered via push March 18, 2026 14:59
@djmbdjmb
pushed 01791b2
main
Status Success
Total duration 3m 9s
Artifacts 2

publish-image.yml

on: push
Matrix: build
Create multi-arch manifest and sign
1m 16s
Create multi-arch manifest and sign
Fit to window
Zoom out
Zoom in

Annotations

9 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@v6.18.0, docker/login-action@v3.5.0, docker/metadata-action@v5.8.0, docker/setup-buildx-action@v3.11.1. 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/
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/
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/
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@v6.18.0, docker/login-action@v3.5.0, docker/metadata-action@v5.8.0, docker/setup-buildx-action@v3.11.1. 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/
Create multi-arch manifest and sign
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.5.0, docker/metadata-action@v5.8.0, docker/setup-buildx-action@v3.11.1. 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/

Artifacts

Produced during runtime
Name Size Digest
basecamp~writebook~5JUIA9.dockerbuild
59.7 KB
sha256:c5bc13305b0bbaccee0a5c701240e38dc05b89c688f907a1049494986926ab25
basecamp~writebook~7PX03N.dockerbuild
58.3 KB
sha256:bc4d9435638313c21188155c51c22569b2694548da0e9f015ec973bf584647aa