Conversation
YanaXu
approved these changes
Feb 22, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recently, we upgraded Node.js version from v16 to v20. And several other dependencies should also be bumped to address scanning alerts. Here are the changes made:
lodashupdated to4.17.21babel/traverseupdated to7.23.9word-wrapupdated to1.2.5xmldom. As it is a dependency ofactions-secret-parser, the version update request has been reported in Bump the version ofxmldomforactions-secret-parsermicrosoft/pipelines-appservice-lib#102. To mitigate the side effect, we've replaced the usage ofactions-secret-parserwith reading the json object directly.