chore(deps): bump cloud.google.com/go/storage from 1.39.1 to 1.48.0 #1438
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
A single node development cluster (infra-pr-1438) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: Further Development☕ If you make changes, you can commit and push and CI will take care of updating the development cluster. 🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
dependabot
bot
force-pushed
the
dependabot/go_modules/cloud.google.com/go/storage-1.48.0
branch
from
1866d8e to
415f845
Compare
Bumps [cloud.google.com/go/storage](https://github.com/googleapis/google-cloud-go) from 1.39.1 to 1.48.0. - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/CHANGES.md) - [Commits](googleapis/google-cloud-go@storage/v1.39.1...spanner/v1.48.0) --- updated-dependencies: - dependency-name: cloud.google.com/go/storage dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/go_modules/cloud.google.com/go/storage-1.48.0
branch
from
415f845 to
68e9eec
Compare
|
Superseded by #1451. |
Pull request was closed
dependabot
bot
deleted the
dependabot/go_modules/cloud.google.com/go/storage-1.48.0
branch
Bumps cloud.google.com/go/storage from 1.39.1 to 1.48.0.
Release notes
Sourced from cloud.google.com/go/storage's releases.
... (truncated)
Commits
37cccafchore(main): release spanner 1.48.0 (#8158)d980b42fix(spanner): reset buffer after abort on first SQL statement (#8440)db6dc5achore: release main (#8428)e5e950btest(internal/docfx): fix expected number of pages in test (#8437)9a0c631chore(policytroubleshooter/iam): add config to generate apiv3 (#8436)2a1455dchore(main): release bigquery 1.54.0 (#8326)e3b9cdcfeat(language): start generating apiv2 (#8434)916f779feat(bigquery/biglake): start generating apiv1 and apiv1alpha1 (#8433)404097efeat(workflows/executions): add UNAVAILABLE and QUEUED to state enum (#8430)b3dbddedocs(optimization): Minor formatting (#8417)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)