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

Do not exceed upper bound of range when using --target semver #1409

Open
raineorshine opened this issue May 10, 2024 · 0 comments
Open

Do not exceed upper bound of range when using --target semver #1409

raineorshine opened this issue May 10, 2024 · 0 comments
Labels

Comments

@raineorshine
Copy link
Owner

This is very useful for keeping my packages up to date, but often I have to set a ceiling version number due to newer versions dropping support for Node versions. However this then makes this tool not useful at all as it ignores that constraint and tells me to update past that which I am incapable of doing.

I want the command to take that ceiling into account and only offer me upgrades that are below the ceiling I have set.
Upgrading past the ceiling point leaves me unable to see when there are genuine patch or minor upgrades etc that I would like to upgrade to.

Example current usage:

 binary-extensions       ^2.2.0  →  ^3.0.0
 commander           ^9.5.0 <10  →     ^12
 cross-fetch          ^3.1.8 <4  →      ^4
 isbinaryfile        ^4.0.10 <5  →      ^5
 typescript         ~5.0.4 <5.1  →    ^5.4

I thought ncu --target semver would do what I like but no.

Is there any usage that does do what I wish it to do?

Thanks

Originally posted by @Nixinova in #1407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant