mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-26 06:05:54 +03:00
[PR #2134] [MERGED] build(deps): bump google.golang.org/api from 0.264.0 to 0.265.0 #2126
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#2126
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/fsouza/fake-gcs-server/pull/2134
Author: @dependabot[bot]
Created: 2/4/2026
Status: ✅ Merged
Merged: 2/4/2026
Merged by: @fsouza
Base:
main← Head:dependabot/go_modules/google.golang.org/api-0.265.0📝 Commits (1)
d1037d4build(deps): bump google.golang.org/api from 0.264.0 to 0.265.0📊 Changes
2 files changed (+6 additions, -6 deletions)
View changed files
📝
go.mod(+2 -2)📝
go.sum(+4 -4)📄 Description
Bumps google.golang.org/api from 0.264.0 to 0.265.0.
Release notes
Sourced from google.golang.org/api's releases.
Changelog
Sourced from google.golang.org/api's changelog.
Commits
e6edc1dchore(main): release 0.265.0 (#3474)afa65b7feat(all): auto-regenerate discovery clients (#3482)0554404chore: Migrate gsutil usage to gcloud storage (#3466)84932f3chore: replace old go teams with cloud-sdk-go-team (#3475)242927achore: Migrate gsutil usage to gcloud storage (#3469)0f1cb7bfeat: add checksums for single chunk json uploads (#3448)e92945dchore: Migrate gsutil usage to gcloud storage (#3470)ba218c1chore: Migrate gsutil usage to gcloud storage (#3468)2e7d0f5chore: Migrate gsutil usage to gcloud storage (#3471)460b37cchore: Migrate gsutil usage to gcloud storage (#3467)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 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)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.