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

Update docker/build-push-action action to v5 - autoclosed #18

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 12, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
docker/build-push-action action major v2.10.0 -> v5.4.0

Release Notes

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

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/docker-build-push-action-5.x branch from f77851c to 33b0727 Compare November 17, 2023 14:26
@renovate renovate bot force-pushed the renovate/docker-build-push-action-5.x branch 2 times, most recently from 74b9b3d to 3840bad Compare March 14, 2024 11:15
@renovate renovate bot force-pushed the renovate/docker-build-push-action-5.x branch from 3840bad to 780c820 Compare June 10, 2024 09:55
@renovate renovate bot changed the title Update docker/build-push-action action to v5 Update docker/build-push-action action to v5 - autoclosed Jun 17, 2024
@renovate renovate bot closed this Jun 17, 2024
@renovate renovate bot deleted the renovate/docker-build-push-action-5.x branch June 17, 2024 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants