-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
npm installing the latest version installs the alpha 4.x and not the stable 3.x #5617
Comments
We use semver b/c that's what npm uses, but it's not an accurate representation of the stability of each Given that we're using semver for npm releases, there are some significant API changes that wouldn't be appropriate to push as a 3.x release. Since the rest of the Selenium project isn't ready for 4.0, I pushed it with the alpha tag. |
I may have misunderstood: is 4 stable? If it is, why does it have an I'm not sure what this has to do with semver. npm enables you to tag the "latest" version as something else than the last version published. This is exactly to enable beta versions that you don't want people to use until they stop being beta: so that Currently, our customers are All you need to do is to npm-tag |
@jleyba says:
The fundamental problem that we users have is simple: the current release pushed to npm is not marked as a stable release. From https://semver.org/#spec-item-9
@jleyba also says:
This is the part that does not make sense. 4.0 is released: you said it is the latest stable and supported version. Adding the If the latest release is stable and supported, please release it as 4.0.0. |
Currently in this npm package, if a developer just does
npm install selenium-webdriver
they will get the 4.x.x-alpha version, which is somewhat unstable. They will get the 4 version because that version is tagged as "latest" in npm (trynpm view selenium-webdriver dist-tags
to see this).I believe that until 4 is out of beta, the latest 3.x.x should be tagged as "latest", while the 4.x.x should be tagged as "beta".
I've been bitten at least three times by this problem, and it takes a while to figure out the problem. Moreover, many of our customers have been having problems because of this issue, so this is not just a theoretical issue.
The text was updated successfully, but these errors were encountered: