mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-25 21:55:56 +03:00
[PR #540] [MERGED] build(deps): bump @google-cloud/storage from 5.8.5 to 5.9.0 in /examples/node #696
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#696
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/540
Author: @dependabot[bot]
Created: 7/21/2021
Status: ✅ Merged
Merged: 7/21/2021
Merged by: @dependabot[bot]
Base:
main← Head:dependabot/npm_and_yarn/examples/node/google-cloud/storage-5.9.0📝 Commits (1)
313e30dbuild(deps): bump @google-cloud/storage in /examples/node📊 Changes
1 file changed (+54 additions, -54 deletions)
View changed files
📝
examples/node/package-lock.json(+54 -54)📄 Description
Bumps @google-cloud/storage from 5.8.5 to 5.9.0.
Release notes
Sourced from
@google-cloud/storage's releases.Changelog
Sourced from
@google-cloud/storage's changelog.Commits
cf53a5echore: release 5.9.0 (#1508)49008e3feat: customize retry behavior implementation (#1474) (#1493)742567bbuild: switch to release-please release tagging (#1129) (#1507)34a747edocs: removed stale note (#1505)9f17909chore(deps): update dependency@types/tmpto v0.2.1 (#1500)f58b50fdocs: specify file ref more precisely (#1498)8903d0ebuild: auto-approve renovate-bot PRs for minor updates (#1145) (#1496)e476961samples: Public access prevention samples and tests (#1310)75541dbbuild(node): do not throw on deprecation (#1140) (#1495)dfd1ec7build(node): don't throw on deprecation in unit tests (#1494)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 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)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.