mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-25 21:55:56 +03:00
[PR #174] [MERGED] build(deps): bump @google-cloud/storage from 4.3.0 to 4.3.1 in /examples/node #403
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#403
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/174
Author: @dependabot-preview[bot]
Created: 2/10/2020
Status: ✅ Merged
Merged: 2/10/2020
Merged by: @dependabot-preview[bot]
Base:
master← Head:dependabot/npm_and_yarn/examples/node/google-cloud/storage-4.3.1📝 Commits (1)
a28a639build(deps): bump @google-cloud/storage in /examples/node📊 Changes
1 file changed (+59 additions, -24 deletions)
View changed files
📝
examples/node/package-lock.json(+59 -24)📄 Description
Bumps @google-cloud/storage from 4.3.0 to 4.3.1.
Release notes
Sourced from @google-cloud/storage's releases.
Changelog
Sourced from @google-cloud/storage's changelog.
Commits
6809490chore: release 4.3.1 (#1048)03494f9chore(deps): update dependency linkinator to v2d6e3738fix: skip validation for server decompressed objects (#1063)fcceecechore: skip img.shields.io in docs teste83d7a6docs(readme): log errors in samplee95ec19fix: unhandled promise rejection warning in samples (#1056)12ff99cchore(deps): update dependency @types/mocha to v7719becachore: generate synth.metadatae9a0ac9chore: clear synth.metadata (#1049)7dc28b3test(system): debug flaky test (#948)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.