fix(deps): update dependency cleye to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cleye	1.3.2 -> 2.0.0

---

Release Notes

privatenumber/cleye (cleye)

v2.0.0

Compare Source

Bug Fixes

• prevent built-in flags from being overridden by user-defined flags (ea22b4c)

Features

• drop node 12 support (e8d992a)
• support async callbacks (6f36731)
• upgrade type-flag (fceceda)

BREAKING CHANGES

• Must use Node 20 (LTS) and above

v1.3.4

Compare Source

Bug Fixes

• handle missing command (534019f)

v1.3.3

Compare Source

Bug Fixes

• improve name validation (846be16), closes #​32

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: d4b33d7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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

---

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to e0fe76c in 3 minutes and 39 seconds. Click for details.

• Reviewed 16 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. package.json:21

• Draft comment:
  The cleye dependency is updated to v2.0.0, which now requires Node 20. Consider adding or updating the "engines" field (e.g., "node": ">=20.0.0") in package.json to enforce this requirement and avoid runtime issues.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This comment is suggesting to add an "engines" field based on a claimed requirement of cleye v2.0.0 needing Node 20. However, I cannot verify this claim from the diff or file contents alone - I would need to check cleye's documentation or package.json. The comment is also somewhat speculative ("consider adding") and is suggesting a preventative measure rather than pointing out a definite issue. According to the rules, I should not make speculative comments or comments about dependency changes. The rule explicitly states "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This is clearly a comment about a dependency change. The comment might actually be correct about cleye v2.0.0's requirements, and adding an engines field could be a legitimate best practice. It's providing actionable advice that could prevent runtime issues for users on older Node versions. While the advice might be sound, the rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This comment is directly about a dependency version change and its implications. Without being able to verify the claim about Node 20 requirement, and given the explicit rule against commenting on dependencies, this comment should be removed. This comment should be deleted because it violates the rule against commenting on dependency changes. The comment is about the implications of updating a dependency version, which falls squarely under "anything else related to dependencies."

Workflow ID: wflow_iyi4lc9wVsU4JXMS

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cleye@​1.3.2 ⏵ 2.0.0				+8

View full report