chore(deps): update dependency inquirer to v12

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
inquirer (source)	^10.0.1 -> ^12.2.0

---

Release Notes

SBoudrias/Inquirer.js (inquirer)

v12.2.0

Compare Source

v12.1.0

Compare Source

v12.0.1

Compare Source

v12.0.0

Compare Source

• @types/node is now only a peerDependencies. This reduces the install size of inquirer dramatically for folks not using Typescript. It's unlikely to break your builds if you used TS already, if it does run npm install --dev @​types/node/yarn add --dev @​types/node.

v11.1.0

Compare Source

• Now exports base utility Typescript types: import type { Question, DistinctQuestion, Answers } from 'inquirer';

You should use as follow to keep the inference working properly:

const questions = [ { ... } ] as const satisfies Question[]; // If you're not using inquirer plugins, `Question` could alternatively be replaced by `DistinctQuestion` for stricter checks.

v11.0.2

Compare Source

• Fix #​1555: when behaviour changed unexpectedly when returning a falsy value.

v11.0.1

Compare Source

v11.0.0

Compare Source

No technical breaking changes; but we changed the style of the question prefix once the answer is provided. Once a question is answer, the prefix becomes a tick mark (previously it was the same ? as when the prompt is idle.)

This is theme-able, and so can be overwritten to with theme.prefix.

v10.2.2

Compare Source

• Fix the filter option not working.
• The signal: AbortSignal didn't work with class based prompts (OSS plugins.) Now it should work consistently with legacy style prompts.

v10.2.1

Compare Source

• Fix expand prompt being broken if a Separator was in the choices array.

v10.2.0

Compare Source

• Includes various fixes & new features to the different built-in prompts
• Fix: Major rework of the Typescript types. Hoping to reduce the amount of finicky type errors (or wrong types) you might've ran into.

v10.1.8

Compare Source

v10.1.7

Compare Source

v10.1.6

Compare Source

v10.1.5

Compare Source

v10.1.4

Compare Source

v10.1.3

Compare Source

v10.1.2

Compare Source

v10.1.1

Compare Source

v10.1.0

Compare Source

• Adds the new { type: 'search' } prompt.

v10.0.4

Compare Source

v10.0.3

Compare Source

v10.0.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 10am on Friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.19%. Comparing base (45ba047) to head (9454823).

Additional details and impacted files

@@ Coverage Diff @@ ## v4 #3208 +/- ## ======================================= Coverage 81.19% 81.19% ======================================= Files 226 226 Lines 18145 18145 Branches 2485 2485 ======================================= Hits 14732 14732 Misses 3395 3395 Partials 18 18 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.