mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-26 06:05:54 +03:00
[PR #234] [MERGED] build(deps): bump cloud.google.com/go/storage from 1.6.0 to 1.7.0 #446
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#446
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/234
Author: @dependabot-preview[bot]
Created: 5/5/2020
Status: ✅ Merged
Merged: 5/5/2020
Merged by: @dependabot-preview[bot]
Base:
master← Head:dependabot/go_modules/cloud.google.com/go/storage-1.7.0📝 Commits (3)
d31329bbuild(deps): bump cloud.google.com/go/storage from 1.6.0 to 1.7.0a290db8go mod tidy6973607fakestorage/upload: fix handling of metadata in resumableUpload📊 Changes
3 files changed (+57 additions, -9 deletions)
View changed files
📝
fakestorage/upload.go(+6 -8)📝
go.mod(+1 -1)📝
go.sum(+50 -0)📄 Description
Bumps cloud.google.com/go/storage from 1.6.0 to 1.7.0.
Release notes
Sourced from cloud.google.com/go/storage's releases.
Commits
8781f63storage: release storage/v1.7.083fa74bpubsub: skip TestIntegration_PublicTopica40174fpubsub: skip TestIntegration_OrderedKeys_JSON3e0909aspanner: increases timeout in TestIntegration_ReadOnlyTransaction.2d911easpanner: fix incorrect instance IDs when deleting instances6cc0f54spanner: clean up test instanceseee5386spanner: clearify docs on Aborted tx2169631spanner: fix timeout+staleness bound for test1466466pubsub: Don't stop subs when topic is stopped in pstest5a20ed8all: auto-regenerate gapicsDependabot 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 will merge this PR once CI passes on it, as requested by @fsouza.
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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.