Update the website with versioned docs #5187
Conversation
|
| @@ -0,0 +1,3 @@ | |||
| [ | |||
| "1.21.0" | |||
There was a problem hiding this comment.
Is there any implication of this for the release process? e.g. need to update a script where instead of just regenerating, you would need to make a copy-paste of the current stuff for backup or future use?
There was a problem hiding this comment.
Yup we'll have to call yarn run docusaurus docs:version <VERSION_NUMBER> while cutting the branch.
|
The only thing that I'm unsure are the snippets where we have I'll address this if it's the case in the future. |
|
Is it now safe to revert the revert of #5160 @cortinico ? |
Yes those files are untouched 👍 |
Heads up: this was never unreverted and is now missing. @marschwar can we re-apply it? |
Fixes #4168
There is not much to review here, other than keeping a look at the website from the preview and make sure no link got broken (that is likely if we were using relative paths around).
By default, users on the website will see the "current" docs which are the latest released version (1.21.0 in this case). Users can switch to "next" to see the current status of the documentation.