Sébastien Lorber

I will have to check with @SimenB or Meta, not sure who manage Google Analytics access for Jest 🤪

Hey, > I used ^2.0.0-beta.14 and got the wrong version According to this tool https://semver.npmjs.com/ there's only one version that matches. Isn't Yarn supposed to implement the exact same rules?...

Yes, I'm not very confident with these range things. Looking at how to deprecate all those legacy canary releases, not sure what's the best way. Executing npm deprecate commands one...

This command seems to have worked: ``` npm deprecate @docusaurus/core@">= 2.0.0-beta" "deprecated canary release, please upgrade" npm deprecate @docusaurus/core@"2.0.0-beta.0 || 2.0.0-beta.1 || 2.0.0-beta.2 || 2.0.0-beta.3 || 2.0.0-beta.4 || 2.0.0-beta.5 ||...

I see, so what was the solution to unlock this? Regenerate the whole lockfile?

Thanks @bourdakos1 Just deprecated all the packages, let me know if you are able to remove those resolutions Hope I didn't break anything 🤪

Agree this is not good for versioned multi-instances! What behavior would you like this to have? How Docusaurus should decide which label to display? If really needed, what kind of...

> It doesn't make much sense to me to display two version dropdowns simultaneously anyways. In the end it's better if we can display dropdowns dynamically based on the active...

Quite similar issue to consider @freef https://github.com/facebook/docusaurus/pull/7409 Note some sites are already using sidebar version dropdowns today: https://apisix.apache.org/docs/apisix/getting-started https://docs.dyte.io/react/quickstart This currently requires swizzling the sidebar and a bit of React...

## TLDR of my Node.js opinion: - 2.0 should be released with >= 16.x ("active".x at 2.0 release time) and preserve support in every 2.x - 3.0.alpha should start dev...