Skip to content

[Snyk] Upgrade cleye from 1.3.4 to 2.0.0#364

Open
kshutkin wants to merge 1 commit intomainfrom
snyk-upgrade-b115c9cf6951b9baace8a21a46734fd7
Open

[Snyk] Upgrade cleye from 1.3.4 to 2.0.0#364
kshutkin wants to merge 1 commit intomainfrom
snyk-upgrade-b115c9cf6951b9baace8a21a46734fd7

Conversation

@kshutkin
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade cleye from 1.3.4 to 2.0.0.

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released 23 days ago.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

Release notes
Package name: cleye
  • 2.0.0 - 2025-11-06

    2.0.0 (2025-11-06)

    Bug Fixes

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

    Features

    BREAKING CHANGES

    • Must use Node 20 (LTS) and above
  • 1.3.4 - 2025-02-11

    1.3.4 (2025-02-11)

    Bug Fixes

from cleye GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade cleye from 1.3.4 to 2.0.0.

See this package in npm:
cleye

See this project in Snyk:
https://app.snyk.io/org/kshutkin/project/5cf89abb-6fc1-49c1-9a05-7feaf6cd578d?utm_source=github&utm_medium=referral&page=upgrade-pr
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Nov 29, 2025

⚠️ No Changeset found

Latest commit: 637563a

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

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.

2 participants