NPM upgrade (#17446)#17589
Open
jfaltermeier wants to merge 2 commits into
Open
Conversation
jfaltermeier
force-pushed
the
jf/npm-upgrade
branch
from
128b878 to
5682b70
Compare
* ran npm upgrade after 1.72.x * Align dependency ranges with resolved versions in package-lock Contributed on behalf of STMicroelectronics
jfaltermeier
force-pushed
the
jf/npm-upgrade
branch
from
5682b70 to
c63158b
Compare
Contributor
Author
Member
|
Thanks for the update, @jfaltermeier! |
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.
What it does
How to test
Look out for regressions
Follow-ups
Breaking changes
Attribution
Contributed on behalf of STMicroelectronics
Review checklist
nlsservice (for details, please see the Internationalization/Localization section in the Coding Guidelines)Reminder for reviewers