From ddc5d25079911a131c66f6e6407317b70f6feb46 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 13 May 2024 08:17:30 +0000 Subject: [PATCH] chore(deps): bump docker/build-push-action Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from f8bc7f46003ef0cf98b715743d86c2f1ccd01436 to 6003d3266a923de06063d23a19bd1c719af997c0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](https://github.com/docker/build-push-action/compare/f8bc7f46003ef0cf98b715743d86c2f1ccd01436...6003d3266a923de06063d23a19bd1c719af997c0) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- .github/workflows/docker.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.yml index 316b5b1..b8ad286 100644 --- a/.github/workflows/docker.yml +++ b/.github/workflows/docker.yml @@ -66,7 +66,7 @@ jobs: # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository. # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step. - name: Build and push Docker image - uses: docker/build-push-action@f8bc7f46003ef0cf98b715743d86c2f1ccd01436 # v5 + uses: docker/build-push-action@6003d3266a923de06063d23a19bd1c719af997c0 # v5 with: context: . push: true