Bumped ADO Node API from 8.1.1 to 11.0.0 #382
Open
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
|
|
polatengin
requested changes
Sep 24, 2024
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.
Updated package azure-devops-node-api from 8.1.1. to 11.0.0 to resolve advisories. #380
https://npmjs.com/advisories/1674
Note: the logs after running "npm install" change from "27 vulnerabilities (10 low, 2 moderate, 15 high)" to "25 vulnerabilities (10 low, 2 moderate, 13 high)."
I am not familiar with tfs-cli at all and couldn't properly test that my changes aren't breaking anything. I looked for the unit tests, but I couldn't find much. I did follow the contributions page and everything ran smoothly. Is there something else I can do to make sure there isn't any damage?
Thanks!