Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade inquirer from 8.2.4 to 8.2.6 #18

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

ngeorger
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade inquirer from 8.2.4 to 8.2.6.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 6 months ago, on 2023-08-02.
Release notes
Package name: inquirer
  • 8.2.6 - 2023-08-02
  • 8.2.5 - 2022-10-24
  • 8.2.4 - 2022-04-28
from inquirer GitHub release notes
Commit messages
Package name: inquirer
  • 30ec048 Publish
  • 728536a Fix coverage on clean clone
  • 516a318 Downgrade wrap-ansi
  • 7a2ade6 Publish
  • 42e9f91 Fix coverage reporting?
  • d53072c Legacy fix default clearing on input (#1177)
  • b41b898 Clean branch to make it work with v8 (last common.js release branch)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@ngeorger ngeorger merged commit a283619 into main Jan 25, 2024
3 checks passed
@ngeorger ngeorger deleted the snyk-upgrade-b407e2ac7582ad904cc5f9085b41d941 branch January 25, 2024 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants