bug: pull yargs back to version 17.7.2#408
Merged
lwasser merged 3 commits intoall-contributors:mainfrom Jan 28, 2026
Merged
Conversation
lwasser
commented
Jan 27, 2026
JoshuaKGoldberg
approved these changes
Jan 27, 2026
Contributor
|
Do you want me to throw together the changes needed for the yargs bump? |
Member
Author
@jdalrymple that would be awesome!! Thank you!! |
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
3 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.
We will be in dependency land for a while until everything is up to date and kcd-scripts is dropped.
SO, this pushes yargs back to 17.2.2. ideally we'd pin it there but that will create a nightmare for users. Luckily we aren't deploying to NPM now so this should just be a patch to ensure the api still works.
What:
Why:
How:
Checklist: