# Pre Release

> 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.

- Skill: `memgraph/pre-release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add memgraph/pre-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/memgraph/pre-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: memgraph (https://skillmd.com/u/memgraph)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/memgraph/pre-release

---


# Pre-release

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.

## When to use

- Right before merging/publishing the documentation release branch
- When asked to prepare the docs site for a new Memgraph version
- When asked to run "pre-release" tasks

## Steps

### 1. Update release note dates

Open `pages/release-notes.mdx` and update the dates on the latest release
headings to today's date.

- Look for headings like `### Memgraph v<version> - <date>` and
  `### Lab v<version> - <date>` near the top of the file (under
  "🚀 Latest release").
- Replace the date with today's date in the same format
  (e.g. `May 6th, 2026` → `May 13th, 2026`).
- Only update entries for the version being released.

### 2. Update direct download links

Open `pages/getting-started/install-memgraph/direct-download-links.mdx` and
replace **every** occurrence of the previous version with the new one.

- The file contains download URLs for Docker, CentOS, Debian, Fedora, Rocky,
  Red Hat, and Ubuntu packages.
- Two patterns need updating:
  - Path segments: `v<old>` → `v<new>` (e.g. `v3.8.1` → `v3.9.0`)
  - File names: `<old>` → `<new>` (e.g. `3.8.1` → `3.9.0`)
- Use a global find-and-replace of the bare old version string (e.g. `3.8.1` →
  `3.9.0`) — this covers both patterns in a single pass.
- Verify the result: every URL in the file should reference only the new
  version.

### 3. Rebuild the site to regenerate the sitemap

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`).