chore(deps): update @inquirer packages and apply npm audit fix - #116
Merged
Conversation
- @inquirer/prompts: ^8.1.0 → ^8.5.2 - @inquirer/search: ^4.0.3 → ^4.2.1 - npm audit fix applied (babel, emnapi, and other transitive deps updated)
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
1 participant
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.
Summary
@inquirer/promptsfrom^8.1.0to^8.5.2@inquirer/searchfrom^4.0.3to^4.2.1npm audit fix— resolved 7 vulnerabilities; updated transitive deps (@babel/*,@emnapi/*, and all@inquirer/*sub-packages)Remaining audit warnings
17 moderate-severity warnings remain in jest's dependency chain (
jest → babel-plugin-istanbul → @istanbuljs/load-nyc-config → js-yaml@3.14.2). These cannot be fixed without a breaking downgrade of jest (30.4.2 → 25.0.0). The vulnerability is a DoS in YAML merge-key parsing, only applies to dev/test tooling, and has no realistic attack vector in this project.Test plan
npm testto verify all tests still passnpm auditoutput shows no new regressions beyond the known jest/js-yaml chain