Open homotechsual opened 10 months ago
Third option I thought of after posting - replace the entire message if there's a major change to just say to check the release announcements rather than say check those and still display the command.
Makes sense 👍
I would go with the 2) option and showing a different message for major versions.
We shouldn't print the upgrade command in this case and just ask user to check the major version blog post instead.
Have you read the Contributing Guidelines on issues?
Motivation
Currently we surface upgrades in the CLI when running any
docusaurus
CLI command with either annpm
oryarn
example invocation. We do this regardless of the version change - so if you're on 2.4.3 you'll get shown commands to upgrade to3.1.0
(at the time of writing!)I'm proposing we do one of two things:
Option 1: Suppress the upgrade message on a major version upgrade.
This has at least one major drawback which is it would essentially hide all knowledge of any update when a major version increment happens.
Option 2: Display a warning message when the update is a major version.
This would seem to be the safer option - maintains visibility of the updates but makes it clear that there are likely extra steps.
Self-service