mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-26 06:05:54 +03:00
[PR #188] [MERGED] build(deps): bump @google-cloud/storage from 4.3.1 to 4.3.2 in /examples/node #416
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#416
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/188
Author: @dependabot-preview[bot]
Created: 3/2/2020
Status: ✅ Merged
Merged: 3/2/2020
Merged by: @dependabot-preview[bot]
Base:
master← Head:dependabot/npm_and_yarn/examples/node/google-cloud/storage-4.3.2📝 Commits (1)
7a365e6build(deps): bump @google-cloud/storage in /examples/node📊 Changes
1 file changed (+41 additions, -66 deletions)
View changed files
📝
examples/node/package-lock.json(+41 -66)📄 Description
Bumps @google-cloud/storage from 4.3.1 to 4.3.2.
Release notes
Sourced from @google-cloud/storage's releases.
Changelog
Sourced from @google-cloud/storage's changelog.
Commits
7a7b612chore: release 4.3.2 (#1091)9f13566test: modernize mocha config (#1059)8725c1bchore(deps): update dependency @types/uuid to v7 (#1092)531050afix(tests): flaky getSignedPolicy tests (#1093)c72d57ffix(deps): update dependency uuid to v7 (#1081)82ab2bbchore: correct .jsdoc.js protos and double quotes (#1088)2cd36bachore: update jsdoc.js (#1086)a6c6d93build: add publish.yml enabling GitHub app for publishes (#1084)97fec02test: fix storage perf benchwrapper (#1082)c584cf0chore(deps): update dependency sinon to v9 (#1080)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)@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.