9292 password : ${{ secrets.DOCKERHUB_TOKEN }}
9393 -
9494 name : Build and push
95- uses : docker/build-push-action@v5
95+ uses : docker/build-push-action@v6
9696 with :
9797 context : .
9898 push : ${{ github.event_name != 'pull_request' }}
@@ -152,7 +152,7 @@ jobs:
152152 password: ${{ secrets.DOCKERHUB_TOKEN }}
153153 -
154154 name: Build and push
155- uses: docker/build-push-action@v5
155+ uses: docker/build-push-action@v6
156156 with:
157157 context: .
158158 push: ${{ github.event_name != 'pull_request' }}
@@ -206,9 +206,6 @@ jobs:
206206 docker:
207207 runs-on: ubuntu-latest
208208 steps:
209- -
210- name: Checkout
211- uses: actions/checkout@v4
212209 -
213210 name: Docker meta
214211 id: meta
@@ -224,11 +221,11 @@ jobs:
224221 type=sha
225222 -
226223 name: Build
227- uses: docker/bake-action@v5
224+ uses: docker/bake-action@v6
228225 with:
229226 files: |
230227 ./docker-bake.hcl
231- ${{ steps.meta.outputs.bake-file }}
228+ cwd:// ${{ steps.meta.outputs.bake-file }}
232229 targets: build
233230` ` `
234231
@@ -271,29 +268,12 @@ similar to the previous one:
271268` ` ` yaml
272269 -
273270 name: Build
274- uses: docker/bake-action@v5
271+ uses: docker/bake-action@v6
275272 with:
276273 files: |
277274 ./docker-bake.hcl
278- ${{ steps.meta.outputs.bake-file-tags }}
279- ${{ steps.meta.outputs.bake-file-labels }}
280- targets: build
281- ` ` `
282-
283- If you're building a [remote Bake definition](https://docs.docker.com/build/bake/remote-definition/)
284- using a [Git context](https://github.com/docker/bake-action?tab=readme-ov-file#git-context),
285- you must specify the location of the metadata-only bake file using a `cwd://`
286- prefix :
287-
288- ` ` ` yaml
289- -
290- name: Build
291- uses: docker/bake-action@v5
292- with:
293- source: "${{ github.server_url }}/${{ github.repository }}.git#${{ github.ref }}"
294- files: |
295- ./docker-bake.hcl
296- cwd://${{ steps.meta.outputs.bake-file }}
275+ cwd://${{ steps.meta.outputs.bake-file-tags }}
276+ cwd://${{ steps.meta.outputs.bake-file-labels }}
297277 targets: build
298278` ` `
299279
@@ -353,7 +333,7 @@ Alternatively, each output is also exported as an environment variable:
353333So it can be used with our [Docker Build Push action](https://github.com/docker/build-push-action/) :
354334
355335` ` ` yaml
356- - uses: docker/build-push-action@v5
336+ - uses: docker/build-push-action@v6
357337 with:
358338 build-args: |
359339 DOCKER_METADATA_OUTPUT_JSON
@@ -945,7 +925,7 @@ that you can reuse them further in your workflow using the [`fromJSON` function]
945925 images: name/app
946926 -
947927 name: Build and push
948- uses: docker/build-push-action@v5
928+ uses: docker/build-push-action@v6
949929 with:
950930 tags: ${{ steps.meta.outputs.tags }}
951931 labels: ${{ steps.meta.outputs.labels }}
@@ -992,7 +972,7 @@ of the `metadata-action`:
992972 images: name/app
993973 -
994974 name: Build and push
995- uses: docker/build-push-action@v5
975+ uses: docker/build-push-action@v6
996976 with:
997977 tags: ${{ steps.meta.outputs.tags }}
998978 annotations: ${{ steps.meta.outputs.annotations }}
@@ -1008,12 +988,12 @@ The same can be done with the [`bake-action`](https://github.com/docker/bake-act
1008988 images: name/app
1009989 -
1010990 name: Build
1011- uses: docker/bake-action@v5
991+ uses: docker/bake-action@v6
1012992 with:
1013993 files: |
1014994 ./docker-bake.hcl
1015- ${{ steps.meta.outputs.bake-file-tags }}
1016- ${{ steps.meta.outputs.bake-file-annotations }}
995+ cwd:// ${{ steps.meta.outputs.bake-file-tags }}
996+ cwd:// ${{ steps.meta.outputs.bake-file-annotations }}
1017997 targets: build
1018998` ` `
1019999
@@ -1039,7 +1019,7 @@ Please consult the documentation of your registry.
10391019 DOCKER_METADATA_ANNOTATIONS_LEVELS: manifest,index
10401020 -
10411021 name: Build and push
1042- uses: docker/build-push-action@v5
1022+ uses: docker/build-push-action@v6
10431023 with:
10441024 tags: ${{ steps.meta.outputs.tags }}
10451025 annotations: ${{ steps.meta.outputs.annotations }}
0 commit comments