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

Bump docker/build-push-action from 1.1.0 to 4.1.1 #378

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 14, 2023

Bumps docker/build-push-action from 1.1.0 to 4.1.1.

Release notes

Sourced from docker/build-push-action's releases.

v4.1.1

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

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

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

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

v3.3.0

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

... (truncated)

Commits
  • 2eb1c19 Merge pull request #880 from crazy-max/fix-inputlist
  • 27376fe update generated content
  • c933000 test: build-arg with hash
  • dac08d4 chore(deps): Bump @​docker/actions-toolkit from 0.3.0 to 0.5.0
  • 44ea916 Merge pull request #875 from docker/dependabot/npm_and_yarn/docker/actions-to...
  • 0167eef update generated content
  • 91bf8bf chore(deps): Bump @​docker/actions-toolkit from 0.2.0 to 0.3.0
  • a799b4d Merge pull request #860 from docker/dependabot/npm_and_yarn/docker/actions-to...
  • 87480bd update generated content
  • f9efed5 Merge pull request #871 from dvdksn/fix/secret-example-link
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot requested a review from johnboyes as a code owner June 14, 2023 08:56
@dependabot dependabot bot added dependencies Pull requests that update a dependency file patch Semantic versioning: backwards compatible bug fixes labels Jun 14, 2023
@johnboyes
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/github_actions/docker/build-push-action-4.1.1 branch from 0027dce to 2e9fa04 Compare August 26, 2023 15:03
@johnboyes
Copy link
Contributor

@dependabot rebase

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 1.1.0 to 4.1.1.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@v1.1.0...v4.1.1)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/github_actions/docker/build-push-action-4.1.1 branch from 2e9fa04 to ce01633 Compare August 28, 2023 12:09
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 8, 2023

Superseded by #395.

@dependabot dependabot bot closed this Sep 8, 2023
@dependabot dependabot bot deleted the dependabot/github_actions/docker/build-push-action-4.1.1 branch September 8, 2023 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file patch Semantic versioning: backwards compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant