Bump docker/build-push-action from 7.1.0 to 7.2.0#114
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 7.1.0 to 7.2.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v7.1.0...v7.2.0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-version: 7.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
||
| - name: Publish 'linux/${{ matrix.platform }}' image by digest | ||
| uses: docker/build-push-action@v7.1.0 | ||
| uses: docker/build-push-action@v7.2.0 |
There was a problem hiding this comment.
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@<full-commit-sha> # v7.2.0`. Apply SHA pinning consistently to actions used in release/publish workflows.</recommendation>
</violation>
</file>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps docker/build-push-action from 7.1.0 to 7.2.0.
Release notes
Sourced from docker/build-push-action's releases.
Commits
f9f3042Merge pull request #1517 from docker/dependabot/npm_and_yarn/docker/actions-t...812d5fdchore: update generated contentb6f6693chore(deps): Bump@docker/actions-toolkitfrom 0.87.0 to 0.90.0c1c626eMerge pull request #1525 from docker/dependabot/npm_and_yarn/actions/core-3.0.151bb284chore: update generated content5f7884dchore(deps): Bump@actions/corefrom 3.0.0 to 3.0.1e01deffMerge pull request #1521 from docker/dependabot/npm_and_yarn/fast-xml-parser-...3804d49chore: update generated content71e8947chore(deps): Bump fast-xml-parser from 5.5.7 to 5.8.04925ad2Merge pull request #1526 from docker/dependabot/npm_and_yarn/postcss-8.5.10You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)