Documentation release process - Besu - LF Decentralized Trust Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window) PreferencesOnly necessaryAccept all LF Decentralized Trust LF Decentralized Trust Spaces Apps Templates Create Besu All content Shortcuts Meetings Meetings  This trigger is hidden How-to articles How-to articles  This trigger is hidden Content Results will update as you type. Code of Conduct Contributing Developing and Conventions Documentation Documentation contribution workflow Documentation contribution guidelines Versioned documentation Documentation archive Documentation release process Documentation style guide Future Release Dates MkDocs and Markdown guide Proposal - Besu maintainers become docs maintainers Raise issues Community Governance Programs & Grants Meetings Design Documents Security Audits Start Here Performance & Stability How-to articles Incident Reports Besu Roadmap & Planning How to Contribute You‘re viewing this with anonymous access, so some content might be blocked. Close Besu / Documentation release process More actions Documentation release process Nicolas Massart Sally MacFarlane Byron Gravenorst +4 Owned by Nicolas Massart Last updated: Aug 19, 2024 by Sally MacFarlane A new stable version of the Besu documentation is released when a new version of the Besu software is released. NOTE: If it's the first time (or if any dependencies have changed), you will need to run yarn install to install Docusaurus You will need node.js version v18.x (use NVM to easily manage node versions). To release the documentation, first run the following command to create a new doc version: npm run docusaurus docs:version (This automatically updates versions.json  file to include the new version number.) Then, in docusaurus.config.js , under presets > classic > docs: Update the lastVersion  to the new version number. Under versions : Add the new version and set its label to stable () . Update the previous version to remove the stable  label. For example, when updating from version 23.4.1  to 23.4.2 , update the following section in docusaurus.config.js  from the following: docusaurus.config.js (before) lastVersion: "23.4.1", versions: { current: { label: "development", path: "development", }, "23.4.1": { label: "stable (23.4.1)", }, "23.4.0": { label: "23.4.0", }, }, To the following: docusaurus.config.js (after) lastVersion: "23.4.2", versions: { current: { label: "development", path: "development", }, "23.4.2": { label: "stable (23.4.2)", }, "23.4.1": { label: "23.4.1", }, "23.4.0": { label: "23.4.0", }, }, commit your changes and push a PR to the besu-docs repo eg https://github.com/hyperledger/besu-docs/pull/1382  When this PR is merged to main, it should trigger a github action which will update https://besu.hyperledger.org/ The final step is to draft and publish a new release including the changelog on github: https://github.com/hyperledger/besu-docs/releases , multiple selections available, Related content More info Collapse Release Process Release Process Besu More like this Versioned documentation Versioned documentation Besu More like this Documentation Documentation Besu More like this Using CalVer for Besu Releases Using CalVer for Besu Releases Besu More like this Changelog Improvement Proposal Changelog Improvement Proposal Besu More like this Building from source Building from source Besu More like this {"serverDuration": 13, "requestCorrelationId": "47202e02e7cc44d0bd60c987aed6063c"}