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 github/dependabot-update-job-proxy/dependabot-update-job-proxy from v2.0.20240815143114 to v2.0.20240816194904 in /docker #1284

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 18, 2024

Bumps github/dependabot-update-job-proxy/dependabot-update-job-proxy from v2.0.20240815143114 to v2.0.20240816194904.

Commits

Dependabot compatibility score

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 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)

@dependabot dependabot bot requested a review from a team as a code owner August 18, 2024 22:31
@dependabot dependabot bot added dependencies Pull requests that update a dependency file docker Pull requests that update Docker code Fanout labels Aug 18, 2024
@pavera
Copy link
Contributor

pavera commented Aug 20, 2024

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 20, 2024

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@pavera
Copy link
Contributor

pavera commented Aug 20, 2024

@dependabot recreate

Bumps [github/dependabot-update-job-proxy/dependabot-update-job-proxy](https:/github/dependabot-update-job-proxy) from v2.0.20240815143114 to v2.0.20240816194904.
- [Commits](https:/github/dependabot-update-job-proxy/commits)

---
updated-dependencies:
- dependency-name: github/dependabot-update-job-proxy/dependabot-update-job-proxy
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/docker/docker/github/dependabot-update-job-proxy/dependabot-update-job-proxy-v2.0.20240816194904 branch from 3328356 to 59000b2 Compare August 20, 2024 14:24
@landongrindheim landongrindheim merged commit 224f421 into main Aug 20, 2024
9 checks passed
@landongrindheim landongrindheim deleted the dependabot/docker/docker/github/dependabot-update-job-proxy/dependabot-update-job-proxy-v2.0.20240816194904 branch August 20, 2024 14:35
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 docker Pull requests that update Docker code Fanout
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants