Skip to content
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

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

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.9.0

Release Notes

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

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

v6.6.1

Compare Source

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

v6.6.0

Compare Source

v6.5.0

Compare Source

v6.4.1

Compare Source

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

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.4.0

Compare Source

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 eea5fb0 to e5a94bc Compare June 28, 2024 05:27
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from e5a94bc to 7026865 Compare July 4, 2024 21:01
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from 836ce6e to a94b892 Compare July 24, 2024 08:48
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch 2 times, most recently from 035df80 to 3e14b04 Compare August 15, 2024 20:59
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 3e14b04 to 893172c Compare September 28, 2024 08:33
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 893172c to c717d8d Compare October 2, 2024 05:43
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