fix: update gcp-metadata to catch a json-bigint security fix #1078
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
google-cla
bot
added
the
cla: yes
Codecov Report
@@ Coverage Diff @@
## master #1078 +/- ##
=======================================
Coverage 91.70% 91.70%
=======================================
Files 21 21
Lines 4145 4145
Branches 497 497
=======================================
Hits 3801 3801
Misses 344 344 Continue to review full report at Codecov.
|
JustinBeckwith
approved these changes
Oct 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: googleapis/nodejs-pubsub#1121
A pub/sub user reported a security vulnerability being pulled in through google-auth-library-nodejs -> gcp_metadata -> json_bigint. This just bumps the minimum gcp_metadata to pull that in.