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

Inverted meanings of --prerelease and --patch? #56

Open
chrisxvin opened this issue Mar 25, 2022 · 0 comments
Open

Inverted meanings of --prerelease and --patch? #56

chrisxvin opened this issue Mar 25, 2022 · 0 comments

Comments

@chrisxvin
Copy link

I'm using version 13.0.4.

From help message we got:

    -p, --prerelease [<pkg,...>]       Consider prerelease versions
    -P, --patch [<pkg,...>]            Consider only up to semver-patch

But I think these two options are inverted.

I have a package(name: my-lib) with versions:

0.2.0-alpha.1
0.2.0-alpha.2
0.2.0-alpha.3
0.2.0

And I have a project with dependency:

"my-lib": "^0.2.0-alpha.1"

Then I execute:

updates -i my-lib --prerelease

I think it should tell "my-lib" can update to "0.2.0-alpha.3", but it returns "0.2.0".

If I execute:

updates -i my-lib --patch

It returns "0.2.0-alpha.3".

So, are they inverted?

PS: My test env is company's intranet, so I cannot post actual screenshots. Sorry.

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

No branches or pull requests

1 participant