Skip to content

Bump docker/metadata-action from 5.10.0 to 6.1.0 #115

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump docker/metadata-action from 5.10.0 to 6.1.0 #115

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ jobs:

- name: Extract metadata for Docker
id: meta
uses: docker/metadata-action@v5.10.0
uses: docker/metadata-action@v6.1.0

@superagent-security superagent-security Bot May 26, 2026

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 metadata action is pinned to a mutable tag

uses: docker/metadata-action@v6.1.0 is tag-pinned.

Pin to a full commit SHA and annotate with # v6.1.0.

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:105">
<priority>P1</priority>
<title>Docker metadata action is pinned to a mutable tag</title>
<evidence>The PR changes the publish workflow from `docker/metadata-action@v5.10.0` to `docker/metadata-action@v6.1.0`. GitHub Actions tags are mutable, so this release/publish workflow could run different action code later if the upstream action tag is retagged or the action repository is compromised.</evidence>
<recommendation>Pin `docker/metadata-action` to the full 40-character commit SHA for the intended `v6.1.0` release, and keep the version as a comment for reviewability, for example: `uses: docker/metadata-action@&lt;full-commit-sha&gt; # v6.1.0`.</recommendation>
</violation>
</file>

with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
flavor: latest=false
Expand Down