Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/publish.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ jobs:
org.opencontainers.image.description=A multi-arch Docker image for the Sure website

- name: Publish 'linux/${{ matrix.platform }}' image by digest
uses: docker/build-push-action@v7.1.0
uses: docker/build-push-action@v7.2.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Docker publish workflow uses a mutable action tag

docker/build-push-action@v7.2.0 is a mutable tag in a publish workflow.

Pin the action to the v7.2.0 commit SHA and keep # v7.2.0 as a comment.

AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.

<file name=".github/workflows/publish.yaml">
<violation number="1" location=".github/workflows/publish.yaml:119">
<priority>P1</priority>
<title>Docker publish workflow uses a mutable action tag</title>
<evidence>The PR updates the publish workflow to `uses: docker/build-push-action@v7.2.0`. This remains pinned to a mutable tag in a Docker publishing path, so a moved or compromised upstream tag could cause the release workflow to execute different action code while building and pushing images.</evidence>
<recommendation>Pin `docker/build-push-action` to the full 40-character commit SHA for the intended v7.2.0 release and keep the version as a comment, e.g. `uses: docker/build-push-action@&lt;full-commit-sha&gt; # v7.2.0`. Apply SHA pinning consistently to actions used in release/publish workflows.</recommendation>
</violation>
</file>

id: build
with:
context: .
Expand Down