fix(cli): update notifier should be shown if current is less than latest

[semoal]

Motivation

Will close #5780

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

Related PRs

(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

[netlify]

✔️ [V2]
Built without sensitive environment variables

🔨 Explore the source changes: 327af61

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61794278a3038f00074f3753

😎 Browse the preview: https://deploy-preview-5798--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟢 Performance	96
🟢 Accessibility	98
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

Lighthouse ran on https://deploy-preview-5798--docusaurus-2.netlify.app/

[slorber]

Thanks

Can you tell me how you tested it works, so that I can also try this locally?

The complicated thing with this is to actually test it reliably :D

[Josh-Cena]

The only case that this PR fixes (I think) is when the package.json version is newer than that in the NPM registry. So maybe update Docusaurus to 2.0.0-beta.9

Edit. No, that doesn't fire the update notifier😅 I have no idea how to reproduce it

[semoal]

Will try to create a repro asap guys, I've looked into the code and makes sense to me the issue itself. It was warning the user when current was different than latest, but current could be higher than latest somehow (dont ask me how). That's why I decided to use the semver util to check if the current is less than latest, we should notify that the user should update.

[slorber]

Let's give it a try, it's hard to test locally but hopefully people won't report this issue again in the future 🤷‍♂️