fix(deps): update dependencies yargs to v17 and yargs-parser to v21 #472
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
ReshetovItsMe
changed the title
bcoe
approved these changes
Jun 15, 2023
mcknasty
pushed a commit
to mcknasty/c8
that referenced
this pull request
Feb 2, 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.
Hi! Made a comment on the previous PR, but since there was no response, I'm reopening it. Could we update these dependencies?
Since
avauses more recent versions for very long time and by adding different sub dependencies could break npm/yarn logic. I don't see any blockers not to update them. Are there any? Thanks!Checklist
npm test, tests passingnpm run test:snap(to update the snapshot)