Upgrade Docusaurus to 2.3.1 #951
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
linked an issue
ghost
force-pushed
the
910-docusaurus-upgrade-to-the-latest-stable-release
branch
from
dba8768 to
9c04e30
Compare
|
Rebased after NodeJS upgrade, ready for review. |
bradjohnl
approved these changes
Mar 6, 2023
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR fix/introduce?
Docusaurus packages are bumped to the latest available version 2.3.1.
Additional context
I went through all release notes for new versions - starting at 2.0.0-beta.17 - and I found 2 breaking changes that applies in our case 💥:
(2.0.0-beta.21) bumped nodejs requirement - will be solved when Require NodeJS 16.14 #949 is merged.Checklist
yarn installandyarn run start.