Bump com.google.cloud:google-cloud-storage from 1.113.1 to 2.43.0 in /plugins/repository-gcs #16043
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [com.google.cloud:google-cloud-storage](https://github.com/googleapis/java-storage) from 1.113.1 to 2.43.0. - [Release notes](https://github.com/googleapis/java-storage/releases) - [Changelog](https://github.com/googleapis/java-storage/blob/main/CHANGELOG.md) - [Commits](googleapis/java-storage@v1.113.1...v2.43.0) --- updated-dependencies: - dependency-name: com.google.cloud:google-cloud-storage dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependabot
dependabot
bot
requested review from
anasalkouz,
andrross,
ashking94,
Bukhtawar,
CEHENKLE,
dblock,
dbwiddis,
gbbafna,
jainankitk,
kotwanikunal,
linuxpi,
mch2,
msfroh,
nknize,
owaiskazi19,
reta,
Rishikesh1159,
sachinpkale,
saratvemulapalli,
shwetathareja,
sohami and
VachaShah
as code owners
Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: dependabot[bot] <[email protected]>
|
❌ Gradle check result for ff5299f: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
….google.cloud-google-cloud-storage-2.43.0 Signed-off-by: gaobinlong <[email protected]>
|
❌ Gradle check result for 26c4a30: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 26c4a30: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
….google.cloud-google-cloud-storage-2.43.0 Signed-off-by: gaobinlong <[email protected]>
|
❌ Gradle check result for f6d7fb4: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for f6d7fb4: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
A newer version of com.google.cloud:google-cloud-storage exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
|
Closing since #16072 is merged. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/gradle/plugins/repository-gcs/com.google.cloud-google-cloud-storage-2.43.0
branch
Bumps com.google.cloud:google-cloud-storage from 1.113.1 to 2.43.0.
Release notes
Sourced from com.google.cloud:google-cloud-storage's releases.
... (truncated)
Changelog
Sourced from com.google.cloud:google-cloud-storage's changelog.
... (truncated)
Commits
9cbb726chore(main): release 2.43.0 (#2686)fef6d60test(deps): update cross product test dependencies (#2707)291a9c6chore: Add Clirr exemptions for Protobuf 4.27.4+ runtime (#2705)c1944dbtest(deps): update cross product test dependencies (#2703)de1de19chore: add@InternalExtensionOnlyto BlobWriteSession (#2702)1dd51c3deps: update dependency com.google.cloud:sdk-platform-java-config to v3.35.0 ...9151ac2fix: github workflow vulnerable to script injection (#2663)a7e4fd6chore: Update generation configuration at Wed Sep 11 02:19:33 UTC 2024 (#2701)3432345chore: attempt to drain gRPC ReadObject stream iterator (#2700)1855308fix: close pending zero-copy responses when Storage#close is called (#2696)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)