> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mem0.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Notes Template

> Format for concise launch summaries with clear CTAs.

# Release Notes Template

Release notes are heartbeat updates. They tell readers what shipped, what needs attention, and where to go for the deep dive fast.

***

## ❌ DO NOT COPY: Guidance & Constraints

* Frontmatter must include `title`, `description`, `icon`, `releaseDate`, and `version`. Add `tags` if you need filters (e.g., `["platform", "oss"]`).
* Lead with a one-sentence headline plus a quick stats table (New features, Fixes, Required action). Keep the TL;DR in an `<Info>` block; use `<Warning>` only for breaking changes or deadlines.
* Organize the body into Highlights, Improvements & fixes (grouped by product), and Known issues. Each bullet links to docs where appropriate.
* When reshaping older release notes, retain the shipped items and shout-outs. Map them to these sections instead of rewriting history.
* Include an Upgrade checklist with concrete next steps. Optional “Community shout-outs” should remain short.
* Two-card CTA at the end, as always: left = deeper reference, right = applied next step.

***

## ✅ COPY THIS: Content Skeleton

Paste the snippet below, swap placeholders, and trim optional sections only once you know they’re unnecessary.

```mdx theme={null}
---
title: [Release title]
description: [1 sentence summary of the release]
icon: "sparkles"
releaseDate: "[YYYY-MM-DD]"
version: "[X.Y]"
tags: ["platform", "oss"] # Optional filters
---

# [Release at a glance]

[Hero sentence that states the biggest win.]

| New features | Fixes | Required action |
| --- | --- | --- |
| [#] | [#] | [Required/Optional + short note] |

<Info>
  **TL;DR**
  - [Highlight #1]
  - [Highlight #2]
  - [Highlight #3]
</Info>

<Warning>
  [Breaking change or deadline reminder. Remove if not needed.]
</Warning>

## Highlights

- **[Feature name]:** [One-sentence benefit]. [Link to doc]
- **[Feature name]:** [One-sentence benefit]. [Link to doc]
- **[Feature name]:** [One-sentence benefit]. [Link to doc]

## Improvements & fixes

**Platform**
- [Improvement sentence with link if relevant.]
- [Fix sentence.]

**Open Source**
- [Improvement sentence.]

**SDKs**
- Python: `[Change summary]`.
- TypeScript: `[Change summary]`.

<Tip>
  [Optional activation hint, e.g., “Enable the feature in Settings → Labs.”]
</Tip>

## Known issues

- **[Issue name]:** `[Status]`. `[Workaround or link].`
- **[Issue name]:** `[Status]`. `[Workaround or link].`

## Upgrade checklist

- [ ] `[Step 1: update package or config]`
- [ ] `[Step 2: run migration or toggle setting]`
- [ ] `[Step 3: verify workflow or metric]`

## Community shout-outs

- [Contributor or team]: `[Short thank-you message].`

{/* DEBUG: verify CTA targets */}

<CardGroup cols={2}>
  <Card
    title="[Deep dive reference]"
    description="[Why readers should open it]"
    icon="book-open"
    href="/[reference-link]"
  />
  <Card
    title="[Apply it next]"
    description="[Set expectation for the follow-up guide or cookbook]"
    icon="rocket"
    href="/[next-link]"
  />
</CardGroup>
```

***

## ✅ Publish Checklist

* [ ] Headline sentence and stats table reflect the release accurately.
* [ ] Every highlight, improvement, and issue links to supporting docs when available.
* [ ] `<Warning>` only appears when a deadline or breaking change exists.
* [ ] Upgrade checklist lists concrete steps (not vague reminders).
* [ ] Exactly two CTA cards at the end with valid links.

## Browse Other Templates

<CardGroup cols={3}>
  <Card title="Quickstart" description="Install → Configure → Add → Search → Delete." icon="rocket" href="/templates/quickstart_template" />

  <Card title="Operation Guide" description="Single task walkthrough with verification checkpoints." icon="circle-check" href="/templates/operation_guide_template" />

  <Card title="Feature Guide" description="Explain when and why to use a capability, not just the API." icon="sparkles" href="/templates/feature_guide_template" />

  <Card title="Concept Guide" description="Define mental models, key terms, and diagrams." icon="brain" href="/templates/concept_guide_template" />

  <Card title="Integration Guide" description="Configure Mem0 alongside third-party tools." icon="plug" href="/templates/integration_guide_template" />

  <Card title="Cookbook" description="Narrative, end-to-end walkthroughs." icon="book-open" href="/templates/cookbook_template" />

  <Card title="API Reference" description="Endpoint specifics with dual-language examples." icon="code" href="/templates/api_reference_template" />

  <Card title="Parameters Reference" description="Accepted fields, defaults, and misuse fixes." icon="list" href="/templates/parameters_reference_template" />

  <Card title="Migration Guide" description="Plan → migrate → validate with rollback." icon="arrow-right" href="/templates/migration_guide_template" />

  <Card title="Release Notes" description="Ship highlights and required CTAs." icon="megaphone" href="/templates/release_notes_template" />

  <Card title="Troubleshooting Playbook" description="Symptom → diagnose → fix." icon="life-buoy" href="/templates/troubleshooting_playbook_template" />

  <Card title="Section Overview" description="Landing pages with card grids and CTA pair." icon="grid" href="/templates/section_overview_template" />
</CardGroup>

<CardGroup cols={2}>
  <Card title="Contribution Hub" description="Review the authoring workflow and linked templates." icon="clipboard-list" href="/platform/contribute" />

  <Card title="Docs Home" description="Return to the platform overview once you’re done." icon="compass" href="/platform/overview" />
</CardGroup>