mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-27 06:35:54 +03:00
[PR #686] [MERGED] build(deps): bump @google-cloud/storage from 5.18.1 to 5.18.2 in /examples/node #826
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#826
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/686
Author: @dependabot[bot]
Created: 2/16/2022
Status: ✅ Merged
Merged: 2/17/2022
Merged by: @fsouza
Base:
main← Head:dependabot/npm_and_yarn/examples/node/google-cloud/storage-5.18.2📝 Commits (1)
5eb321bbuild(deps): bump @google-cloud/storage in /examples/node📊 Changes
1 file changed (+20 additions, -20 deletions)
View changed files
📝
examples/node/package-lock.json(+20 -20)📄 Description
Bumps @google-cloud/storage from 5.18.1 to 5.18.2.
Release notes
Sourced from
@google-cloud/storage's releases.Changelog
Sourced from
@google-cloud/storage's changelog.Commits
0682b93chore(main): release 5.18.2 (#1785)1e72586fix: resumable uploads should respect autoRetry & multipart uploads should co...6ce9a2achore: fix linter problem with implicit returns (#1784)04791c7docs(nodejs): version support policy edits (#1346) (#1777)56f2c5bchore: update testbench to v0.14.0 (#1778)c42e7d5chore: Removed double semicolon (#1768)e704c57test: Replace cached test binary with generated file (#1774)e543979chore(deps): update dependency@types/concat-streamto v2 (#1773)5f35999test: run conformance tests in parallel (#1766)9628d40chore(deps): update dependency sinon to v13 (#1772)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 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.