Closed jrappen closed 2 years ago
We never ask users to install deprecated version. Do you know what "deprecated" means - don't use it. Please use lockfile when using CI
Using "vuepress": "^2.0.0-beta.49"
in package.json
results in the above.
Same with all other packages used from your org.
Please use lockfile when using CI
I have the same problem and I can't use it now. I had this problem in both version 48 , 49 and latest 50.
Ok, ^50 will always point to the deprecated version. Just delete ^
.
Looking at:
this should be resolved once 2.0.0-beta.51
or later is released, assuming this is an issue related to sorting where 2.0.0-beta.50-pre.1
and 2.0.0-beta.50-pre
take precedence over 2.0.0-beta.50
.
Forcing users to use a lockfile with CI is diverting from the problem, as the problem is the dev pushing a non-standard semver release tag.
You could either wait for the next release with a valid semver release tag.
... or change to "vuepress": "next"
in the meantime, though that might cause you problems when stable builds finally are released.
As beta.50 has lots of breaking changes, we published some pre versions to test with npm. Didn't realize that package managers will still resolve to non-standard & deprecated version 🤔 We should unpublish them in time.
If you change ^x
to x
, you'll be stuck on x
.
@meteorlxy Reading https://semver.org/lang/zh-CN/ might help you to understand why this happened.
@ykla FYI, beta 51 is also broken
Description
deprecated
v2.0.0-beta.50-pre.1
tag onnpm
breaks CI on GitHub.Also:
This is not the first time this has happened with the
vuepress
project, where a broken random tag is pushed tonpm
but missing on GitHub. Please fix your workflow to make sure this doesn't happen in the future as it breaks CI.Reproduction
any
Used Package Manager
yarn
v1.22.19
System Info