Update dependency @inquirer/confirm to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@inquirer/confirm (source)	3.2.0 → 6.0.10

---

Release Notes

SBoudrias/Inquirer.js (@​inquirer/confirm)

v6.0.10

Compare Source

v6.0.9

Compare Source

v6.0.8

Compare Source

v6.0.7

Compare Source

v6.0.6

Compare Source

v6.0.5

Compare Source

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.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.

v5.1.21

Compare Source

v5.1.20

Compare Source

v5.1.19

Compare Source

v5.1.18

Compare Source

v5.1.17

Compare Source

v5.1.16

Compare Source

v5.1.15

Compare Source

• Fix Unix yes not properly being processed by the confirm prompt. (yes | node confirm-script.js)

v5.1.14

Compare Source

v5.1.13

Compare Source

v5.1.12

Compare Source

v5.1.11

Compare Source

v5.1.10

Compare Source

v5.1.9

Compare Source

v5.1.8

Compare Source

v5.1.7

Compare Source

v5.1.6

Compare Source

v5.1.5

Compare Source

v5.1.4

Compare Source

v5.1.3

Compare Source

v5.1.2

Compare Source

v5.1.1

Compare Source

v5.1.0

Compare Source

• Feat (select): Cursor will now hover disabled options of the list; but they still cannot be interacted with. This prevents the cursor jumping ahead in ways that can be confusing.

v5.0.2

Compare Source

v5.0.1

Compare Source

• Fix: breaking change wrongly removed the Separator export.

v5.0.0

Compare Source

• [Breaking #​1384] @inquirer/core isn't exported from @inquirer/prompts anymore. If you want to create custom prompts, import from the core package. This decision was made to disambiguate what breaks in each package - with prompts re-exporting core, any core breaking change (no matter how minor) caused a major version bump. Now only prompts interfaces breaking changes will be major on prompts. We're hoping this will simplify your usage of @inquirer/* packages.

v4.0.1

Compare Source

• Update dependency to fix a LGPL license issue.

v4.0.0

Compare Source

Breaking

The core codebase went through a major es5 to 6 refactor. As such, we're dropping support for Node 4.

This change will likely require changes to the community Plugins as es6 classes are enforcing more restriction (like constructor can only be invoked with new).

New features / Bug fixes

• list, expand and rawlist prompts now accepts the value as default (previously it would only accept the choice index).
• The pagination now properly handles multiline choices.
• Fix bug where invalid default choices would break the UI.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Never, 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.

[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.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Test
• Failed Step: Run yarn test
• Run: View failed run
  What failed: Uncaught exception during test execution due to invalid data deserialization
  Why: The error message indicates that there was an uncaught exception during the test execution, caused by an issue with deserializing cloned data. This is likely a code-related issue, as it occurred within the application code being tested.
  Action:
  The author should investigate the root cause of the deserialization error and fix the issue in the application code. This may involve reviewing the code that handles the cloned data and ensuring that it is properly serialized and deserialized.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: Test
• Failed Step: Run yarn test
• Run: View failed run
  What failed: CI failure - likely code issue
  Why: The failure appears to be related to code changes. Check the error output for details.
  Action:
  Review the error logs and fix the issue in your code.