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

build(deps): bump the github-actions group across 1 directory with 3 updates #1265

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 19, 2025

Bumps the github-actions group with 3 updates in the / directory: docker/metadata-action, docker/build-push-action and actions/attest-build-provenance.

Updates docker/metadata-action from 5.5.1 to 5.6.1

Release notes

Sourced from docker/metadata-action's releases.

v5.6.1

Full Changelog: docker/metadata-action@v5.6.0...v5.6.1

v5.6.0

Full Changelog: docker/metadata-action@v5.5.1...v5.6.0

Commits
  • 369eb59 Merge pull request #480 from crazy-max/back-to-sha-7
  • 7d870ce chore: update generated content
  • e44a9cd back to commit sha length of 7
  • 8cb0002 Merge pull request #478 from crazy-max/commit-date-request
  • e01ddd3 chore: update generated content
  • 861d98a commiter_date: fix github api request fallback
  • 359e915 Merge pull request #475 from crazy-max/commit-date-changes
  • 0c395eb commit_date: code cleanup and readme updates
  • 1156622 Merge pull request #474 from docker/dependabot/npm_and_yarn/cross-spawn-7.0.5
  • 95ea8d0 chore(deps): Bump cross-spawn from 7.0.3 to 7.0.5
  • Additional commits viewable in compare view

Updates docker/build-push-action from 6.9.0 to 6.12.0

Release notes

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

v6.12.0

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

v6.11.0

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

v6.10.0

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

Commits
  • 67a2d40 Merge pull request #1300 from docker/dependabot/npm_and_yarn/docker/actions-t...
  • 0b1b1c9 chore: update generated content
  • b6a7c2c chore(deps): Bump @​docker/actions-toolkit from 0.49.0 to 0.51.0
  • 31ca4e5 Merge pull request #1296 from crazy-max/bake-v6
  • e613db9 update bake-action to v6
  • b32b51a Merge pull request #1281 from docker/dependabot/npm_and_yarn/docker/actions-t...
  • 594bf46 Merge pull request #1294 from crazy-max/fix-e2e
  • fd37bd5 ci(e2e): fix setup docker config
  • e6478a2 chore: update generated content
  • 78785bd chore(deps): Bump @​docker/actions-toolkit from 0.46.0 to 0.49.0
  • Additional commits viewable in compare view

Updates actions/attest-build-provenance from 1.4.4 to 2.1.0

Release notes

Sourced from actions/attest-build-provenance's releases.

v2.1.0

What's Changed

Full Changelog: actions/attest-build-provenance@v2.0.1...v2.1.0

v2.0.1

What's Changed

Full Changelog: actions/attest-build-provenance@v2.0.0...v2.0.1

v2.0.0

The attest-build-provenance action now supports attesting multiple subjects simultaneously. When identifying multiple subjects with the subject-path input a single attestation is created with references to each of the supplied subjects, rather than generating separate attestations for each artifact. This reduces the number of attestations that you need to create and manage.

What's Changed

Full Changelog: actions/attest-build-provenance@v1.4.4...v2.0.0

Commits
  • 7668571 add attestation-id and attestation-url outputs (#415)
  • 9ad33ff add note about gh plans supporting attestations (#414)
  • f2f0851 Bump the npm-development group with 2 updates (#412)
  • c4fbc64 bump actions/attest from 2.0.0 to 2.0.1 (#406)
  • 619dbb2 bump actions/attest to v2.0.0 (#321)
  • 90d4930 Bump the npm-development group with 3 updates (#329)
  • fb315c1 Bump the npm-development group with 5 updates (#323)
  • a379071 Bump cross-spawn from 7.0.3 to 7.0.6 (#319)
  • dada0c3 Bump the npm-development group across 1 directory with 5 updates (#317)
  • See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…updates

Bumps the github-actions group with 3 updates in the / directory: [docker/metadata-action](https://github.com/docker/metadata-action), [docker/build-push-action](https://github.com/docker/build-push-action) and [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance).


Updates `docker/metadata-action` from 5.5.1 to 5.6.1
- [Release notes](https://github.com/docker/metadata-action/releases)
- [Commits](docker/metadata-action@8e5442c...369eb59)

Updates `docker/build-push-action` from 6.9.0 to 6.12.0
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@4f58ea7...67a2d40)

Updates `actions/attest-build-provenance` from 1.4.4 to 2.1.0
- [Release notes](https://github.com/actions/attest-build-provenance/releases)
- [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md)
- [Commits](actions/attest-build-provenance@ef24412...7668571)

---
updated-dependencies:
- dependency-name: docker/metadata-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: actions/attest-build-provenance
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 19, 2025
@dependabot dependabot bot requested a review from a team January 19, 2025 22:26
@v1v v1v merged commit 374b3e3 into main Jan 20, 2025
234 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/github-actions-4245f47fda branch January 20, 2025 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-php dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant