// Run final pre-release tasks for the documentation site. Updates release note dates, direct download links to the new Memgraph version, and rebuilds the site to regenerate the sitemap. Use when preparing a documentation release, before publishing, or when asked to run "pre-release" steps.
Run before every release to ensure all merged memgraph PRs have a docs label assigned, have changelog entries, have docs pages where required, that all changed text is free of spelling and grammar issues, and that existing documentation cross-links the new content. Use when preparing a release branch, before merging into the main branch, or when asked to "check before release". Also use standalone when asked to audit docs labels on a milestone.
Create a new release branch for Memgraph documentation with the initial release-notes scaffold commit and PR. Use when the user wants to start a new release, create a release branch, or prepare release notes for a new version.
Create/write the changelog item / release note for a given Github PR and update the docs release PR description.
| name | pre-release |
| description | Run final pre-release tasks for the documentation site. Updates release note dates, direct download links to the new Memgraph version, and rebuilds the site to regenerate the sitemap. Use when preparing a documentation release, before publishing, or when asked to run "pre-release" steps. |
Run these steps right before publishing a new documentation release to ensure release dates are correct, download links point to the latest Memgraph version, and the sitemap is up-to-date.
Open pages/release-notes.mdx and update the dates on the latest release
headings to today's date.
### Memgraph v<version> - <date> and
### Lab v<version> - <date> near the top of the file (under
"🚀 Latest release").May 6th, 2026 → May 13th, 2026).Open pages/getting-started/install-memgraph/direct-download-links.mdx and
replace every occurrence of the previous version with the new one.
v<old> → v<new> (e.g. v3.8.1 → v3.9.0)<old> → <new> (e.g. 3.8.1 → 3.9.0)3.8.1 →
3.9.0) — this covers both patterns in a single pass.Run pnpm build from the documentation root. The postbuild script
(next-sitemap) regenerates sitemap.xml automatically.
Confirm the build finishes successfully and the sitemap generation summary
appears at the end of the output (look for [next-sitemap] Generation completed).