O Docusaurus possui um sistema de liberação canário.
It permits you to test new unreleased features as soon as the pull requests are merged on the next version of Docusaurus.
É uma boa maneira de dar feedback aos mantenedores, garantindo que o recurso recém-implementado funcione como deveria.
Using a canary release in production might seem risky, but in practice, it's not.
A canary release passes all automated tests and is used in production by the Docusaurus site itself.
The canary version shown below may not be up-to-date. Please go to the npm page to find the actual version name.
Tag canário npm dist
For any code-related commit on
main, the continuous integration will publish a canary release under the
@canary npm dist tag. It generally takes up to 10 minutes.
You can see on npm the current dist tags:
latest: stable releases (Current: 3.0.0-beta.0)
canary: canary releases (Example: 0.0.0-4922)
Make sure to use the latest canary release and check the publication date (sometimes the publish process fails).
Canary versions follow the naming convention
Usando um lançamento canário
Take the latest version published under the canary npm dist tag (Example: 0.0.0-4922).
Use it for all the
@docusaurus/* dependencies in your
- "@docusaurus/core": "^3.0.0-beta.0",
- "@docusaurus/preset-classic": "^3.0.0-beta.0",
+ "@docusaurus/core": "0.0.0-4922",
+ "@docusaurus/preset-classic": "0.0.0-4922",
Then, install the dependencies again and start your site:
You can also upgrade the
@docusaurus/* packages with command line:
npm install --save-exact @docusaurus/core@canary @docusaurus/preset-classic@canary
yarn add --exact @docusaurus/core@canary @docusaurus/preset-classic@canary
pnpm add --save-exact @docusaurus/core@canary @docusaurus/preset-classic@canary
Make sure to include all the
For canary releases, prefer using an exact version instead of a semver range (avoid the