⚠️ATTENTION: Using version range like ^ or ~ for packages in this repo will fail.

[Mister-Hope]

Description

If you use ^2.0.0-beta.xx for any packages in this repo, you may get an installation failure, or you may get your app broke when upgrading to latest next version.

This is because we published 2 test versions 2.0.0-beta.50-pre.0, 2.0.0-beta.50-pre.1, while 50-pre.x is higher than any number xx.

Solution

The easiest way to solve this is to upgrade vuepress with vp-update.

For:

npx vp-update

yarn dlx vp-update

pnpm dlx vp-update

Manual solution

You can solve this issue by specifying exact version in package.json. e.g.:

{
  "dependencies": {
    "@vuepress/client": "2.0.0-beta.62",
    "vue": "^3.3.4",
    "vuepress": "2.0.0-beta.62"
  }

Note that all the ^ or ~ marker shall be changed for packages in this repo, but you can keep others as is.

{
  "dependencies": {
-    "@vuepress/client": "~2.0.0-beta.62",
-    "@vuepress/client": "^2.0.0-beta.62",
+    "@vuepress/client": "2.0.0-beta.62",
    "vue": "^3.3.4",
-    "vuepress": "~2.0.0-beta.62",
-    "vuepress": "^2.0.0-beta.62",
+    "vuepress": "2.0.0-beta.62"
  }

Also you can use next tag (But we do not recommend this because we may introduce breaking changes in future versions)

{
  "dependencies": {
    "@vuepress/client": "next",
    "vue": "^3.3.4",
    "vuepress": "next"
  }

[init-qy]

If use Renovate to manage package version, this configure may be helpful.

"packageRules": [
    {
      "packageNames": ["vuepress", "@vuepress/client", "@vuepress/markdown", "@vuepress/utils"],
      "allowedVersions": "!/pre.*$/"
    }
]

[Mister-Hope]

If use Renovate to manage package version, this configure may be helpful.

"packageRules": [

    {

      "packageNames": ["vuepress", "@vuepress/client"],

      "allowedVersions": "!/pre.*$/"

    }

]

Other official plug-in may be included as well

[domnantas]

Are there any plans to officially release v2? It has been in beta for 2+ years

[GreenImp]

If 2.0.0-beta.50-pre.0, and 2.0.0-beta.50-pre.1 are no longer needed, a potential solution would be to deprecate them in npm, which should stop them from being installed:

https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions#deprecating-a-single-version-of-a-package

Something like this should do the trick:

npm deprecate [email protected] "Old test version"
npm deprecate [email protected] "Old test version"

[Mister-Hope]

We already deprecated them, and deprecated version won't stop package manager installing them.

[jrappen]

Jumping to v2.0.1-beta.1 would be an option.

[Mister-Hope]

Jumping to v2.0.1-beta.1 would be an option.

Absolutely that could not be an option, what's the difference between yours and v2.0.0?

That's far worse than a version number like v2.0.0-chi.0 or v2.0.0-delta.0

[github-actions]

This issue is marked as stale because it has not had recent activity. Issues marked with stale will be closed if they have no activity within 7 days.