Skip to content

chore(deps): update docker/build-push-action action to v6 #68

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.

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 19, 2024

This PR contains the following updates:

Package Type Update Change
docker/build-push-action action major v2.10.0 -> v6.16.0

Release Notes

docker/build-push-action (docker/build-push-action)

v6.16.0

Compare Source

v6.15.0

Compare Source

Full Changelog: docker/build-push-action@v6.14.0...v6.15.0

v6.14.0

Compare Source

Full Changelog: docker/build-push-action@v6.13.0...v6.14.0

v6.13.0

Compare Source

Full Changelog: docker/build-push-action@v6.12.0...v6.13.0

v6.12.0

Compare Source

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0

v6.11.0

Compare Source

Full Changelog: docker/build-push-action@v6.10.0...v6.11.0

v6.10.0

Compare Source

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

v6.9.0

Compare Source

Full Changelog: docker/build-push-action@v6.8.0...v6.9.0

v6.8.0

Compare Source

Full Changelog: docker/build-push-action@v6.7.0...v6.8.0

v6.7.0

Compare Source

Full Changelog: docker/build-push-action@v6.6.1...v6.7.0

v6.6.1

Compare Source

Full Changelog: docker/build-push-action@v6.6.0...v6.6.1

v6.6.0

Compare Source

Full Changelog: docker/build-push-action@v6.5.0...v6.6.0

v6.5.0

Compare Source

Full Changelog: docker/build-push-action@v6.4.1...v6.5.0

v6.4.1

Compare Source

Full Changelog: docker/build-push-action@v6.4.0...v6.4.1

v6.4.0

Compare Source

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

v6.3.0

Compare Source

Full Changelog: docker/build-push-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

Full Changelog: docker/build-push-action@v6.1.0...v6.2.0

v6.1.0

Compare Source

Full Changelog: docker/build-push-action@v6.0.2...v6.1.0

v6.0.2

Compare Source

Full Changelog: docker/build-push-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

Full Changelog: docker/build-push-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

[!NOTE]
This major release adds support for generating Build summary and exporting build record for your build. You can disable this feature by setting DOCKER_BUILD_SUMMARY: false environment variable in your workflow.

Full Changelog: docker/build-push-action@v5.4.0...v6.0.0

v5.4.0

Compare Source

Full Changelog: docker/build-push-action@v5.3.0...v5.4.0

v5.3.0

Compare Source

Full Changelog: docker/build-push-action@v5.2.0...v5.3.0

v5.2.0

Compare Source

Full Changelog: docker/build-push-action@v5.1.0...v5.2.0

v5.1.0

Compare Source

Full Changelog: docker/build-push-action@v5.0.0...v5.1.0

v5.0.0

Compare Source

Full Changelog: docker/build-push-action@v4.2.1...v5.0.0

v4.2.1

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v4.2.0...v4.2.1

v4.2.0

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v4.1.1...v4.2.0

v4.1.1

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v4.1.0...v4.1.1

v4.1.0

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v4.0.0...v4.1.0

v4.0.0

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v3.3.1...v4.0.0

v3.3.1

Compare Source

Full Changelog: docker/build-push-action@v3.3.0...v3.3.1

v3.3.0

Compare Source

Note

Buildx v0.10 enables support for a minimal SLSA Provenance attestation, which requires support for OCI-compliant multi-platform images. This may introduce issues with registry and runtime support (e.g. Google Cloud Run and AWS Lambda). You can optionally disable the default provenance attestation functionality using provenance: false.

Full Changelog: docker/build-push-action@v3.2.0...v3.3.0

v3.2.0

Compare Source

Full Changelog: docker/build-push-action@v3.1.1...v3.2.0

v3.1.1

Compare Source

Full Changelog: docker/build-push-action@v3.1.0...v3.1.1

v3.1.0

Compare Source

Full Changelog: docker/build-push-action@v3.0.0...v3.1.0

v3.0.0

Compare Source

Full Changelog: docker/build-push-action@v2.10.0...v3.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from fc7aed9 to 14abef8 Compare June 27, 2024 02:28
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 14abef8 to 3da6cee Compare July 3, 2024 08:52
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 3 times, most recently from 08f8e3f to f15f744 Compare July 24, 2024 00:03
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from 53103c8 to 205516f Compare August 13, 2024 23:58
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from 37a7325 to a3d7239 Compare October 1, 2024 05:10
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from a3d7239 to aded4ff Compare November 26, 2024 20:56
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from 7421704 to 5df8e7a Compare January 15, 2025 19:30
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 5df8e7a to 91ce240 Compare January 25, 2025 03:18
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 91ce240 to ab590d4 Compare February 21, 2025 03:27
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from ab590d4 to 694bdc8 Compare February 28, 2025 08:01
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 694bdc8 to 5898b24 Compare April 27, 2025 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants