Skip to content

Bump the github-actions group with 2 updates - #91

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/github-actions-fd8fae8294
Closed

Bump the github-actions group with 2 updates#91
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/github-actions-fd8fae8294

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 24, 2026

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 2 updates: actions/checkout and actions/setup-java.

Updates actions/checkout from 7.0.0 to 7.0.1

Release notes

Sourced from actions/checkout's releases.

v7.0.1

What's Changed

Full Changelog: actions/checkout@v7...v7.0.1

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.1

v7.0.0

v6.0.3

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

... (truncated)

Commits

Updates actions/setup-java from 5.4.0 to 5.6.0

Release notes

Sourced from actions/setup-java's releases.

v5.6.0

What's Changed

Full Changelog: actions/setup-java@v5...v5.6.0

v5.5.0

What's Changed

New Contributors

Full Changelog: actions/setup-java@v5...v5.5.0

Commits
  • 03ad4de Backport #1097/#1098: cache Maven and Gradle wrapper distributions separately...
  • d229d2e Backport #1111: Preserve Maven toolchains across repeated setup-java runs (#1...
  • bbf0f69 dist: Cover Tencent Kona JDK 25 (#1110)
  • 513edc4 feat: expose cache-primary-key output (#597) [v5 backport] (#1089)
  • 62df799 Add Maven compiler problem matcher for javac diagnostics (#1087)
  • 176156a chore: bump version to 5.6.0 for v5 release line
  • bf7b8de build: rebuild dist for backported changes (#1079, #1083, #1084)
  • 0173e6d Infer distribution from asdf .tool-versions vendor prefix (#1084)
  • f45cd82 Rename jdkFile input to jdk-file with deprecated alias (#1083)
  • e2863ad Map Zulu x86 architecture to i686 for Azul Metadata API (#1079)
  • Additional commits viewable 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 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

Bumps the github-actions group with 2 updates: [actions/checkout](https://github.com/actions/checkout) and [actions/setup-java](https://github.com/actions/setup-java).


Updates `actions/checkout` from 7.0.0 to 7.0.1
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@9c091bb...3d3c42e)

Updates `actions/setup-java` from 5.4.0 to 5.6.0
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](actions/setup-java@1bcf9fb...03ad4de)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: actions/setup-java
  dependency-version: 5.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 24, 2026
@cgdecker

Copy link
Copy Markdown
Member

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

I can't perform the requested action because I don't have any knowledge about this pull request.

@cgdecker

Copy link
Copy Markdown
Member

@dependabot recreate

@dependabot @github

dependabot Bot commented on behalf of github Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

I can't perform the requested action because I don't have any knowledge about this pull request.

@cpovirk

cpovirk commented Jul 30, 2026

Copy link
Copy Markdown
Member

Weirdness all around here:

On the lack of an import CL

Copybara reported last week that this PR is a no-op because Dependabot hasn't signed the CLA? What is special about this Dependabot PR compared to any other Dependabot PR?

Maybe the CLA bot just failed to run here? I see a run in the Checks on a pending Copybara PR and in an already-imported Dependabot PR. I think there was some GitHub trouble recently, so maybe that aligns with the missed CLA-bot run.

Regardless, I thought that normally we got a Copybara link in the Checks section, but I don't see one here. I had to pull up the PR manually in the internal Copybara UI. Now that I think about it, I guess that the link is normally to the generated CL, so "no CL, no link?" But then I thought I'd seen Copybara errors in the Checks section before, so I'd still expect to see something.

I see "feedback/copybara" and "import/copybara" (the latter twice) in a pending Truth PR. I don't see those at all in the PRs here. In fairness, I don't see them in an already imported Truth PR, so that doesn't help us distinguish whether there's something weird about this PR or about guava-beta-checker in general.

On "I can't perform the requested action because I don't have any knowledge about this pull request"

By the time cgdecker sent commands, maybe had Dependabot finally decided that it shouldn't have done some of this at all until after the cooldown?

Now, Dependabot was willing to rebase a Truth PR. But the upgrade there was to a package that was released 11 days ago (so past the cooldown cutoff), and maybe more importantly, it was created later than this one, so maybe it was created under the new cooldown configuration?

To-do

My plan at this point is to see if closing the PR helped :) Normally, closing a Dependabot PR discourages Dependabot from... maybe not much, at least for the "group" configuration that we have in place. So we might see this same change re-created soon, especially since Dependabot has disowned this PR. Or maybe Dependabot will wait until there's something else to upgrade or at least until its future weekly run?

I see Copybara Service and Google CLA installed for guava-beta-checker, just as it is for truth, so I don't think there's anything to change there, especially since both seemed to be working fine here up until this CL. And while I see that Truth has some branch-protection rules, that doesn't include anything for Copybara or Google CLA specifically AFAICT (like, no required status checks for either), so I wouldn't expect that to affect whether we see anything related to those in the list of Checks.

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 github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants