Bump the github-actions group with 2 updates - #91
Conversation
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 rebase |
|
I can't perform the requested action because I don't have any knowledge about this pull request. |
|
@dependabot recreate |
|
I can't perform the requested action because I don't have any knowledge about this pull request. |
|
Weirdness all around here: On the lack of an import CLCopybara 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 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-doMy 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 |
Bumps the github-actions group with 2 updates: actions/checkout and actions/setup-java.
Updates
actions/checkoutfrom 7.0.0 to 7.0.1Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
3d3c42eprep v7.0.1 release (#2531)2880268escape values passed to --unset (#2530)12cd223trim only ascii whitespace for branch (#2521)62661c4skip running unsafe pr check if input is default (#2518)e8d4307Bump the minor-actions-dependencies group with 2 updates (#2499)631c942eslint 9 (#2474)4f1f4aeBump actions/upload-artifact from 4 to 7 (#2476)ba09753Bump actions/checkout from 6 to 7 (#2488)b9e0990Bump docker/login-action from 3.3.0 to 4.2.0 (#2479)e8cb398Bump docker/build-push-action from 6.5.0 to 7.2.0 (#2478)Updates
actions/setup-javafrom 5.4.0 to 5.6.0Release notes
Sourced from actions/setup-java's releases.
Commits
03ad4deBackport #1097/#1098: cache Maven and Gradle wrapper distributions separately...d229d2eBackport #1111: Preserve Maven toolchains across repeated setup-java runs (#1...bbf0f69dist: Cover Tencent Kona JDK 25 (#1110)513edc4feat: expose cache-primary-key output (#597) [v5 backport] (#1089)62df799Add Maven compiler problem matcher for javac diagnostics (#1087)176156achore: bump version to 5.6.0 for v5 release linebf7b8debuild: rebuild dist for backported changes (#1079, #1083, #1084)0173e6dInfer distribution from asdf .tool-versions vendor prefix (#1084)f45cd82Rename jdkFile input to jdk-file with deprecated alias (#1083)e2863adMap Zulu x86 architecture to i686 for Azul Metadata API (#1079)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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