Added Release note for customer reference

[nagstler]

Added Release Notes section

Summary by CodeRabbit

• New Features
  • Added a new "Releases" navigation link in the top navigation bar, providing quick access to release notes documentation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A single topbar link entry is added to the mint.json configuration file, introducing a new "Releases" link pointing to the "release-notes" page in the navigation bar.

Changes

Cohort / File(s)	Change Summary
Configuration Update mint.json	Added new topbar link entry {"name": "Releases", "url": "release-notes"} to the topbarLinks array

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A link to releases, fresh and bright,
Now hops into view, just right!
One small addition, easy to see,
Release notes flowing, wild and free! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Added Release note for customer reference' is partially related to the changeset. The PR adds a topbar link to 'Releases' in mint.json, which is infrastructure for a release notes section rather than the actual release notes content itself.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/api-reference

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87a4b79 and 6b5278d.

📒 Files selected for processing (1)

• mint.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check mint.json structure and search for release-notes files

# First, find and examine mint.json
echo "=== Checking for mint.json ==="
find . -name "mint.json" -type f | head -5

echo -e "\n=== Checking for release-notes files ==="
# Search for release-notes pages
find . -type f \( -name "*.mdx" -o -name "*.md" \) | grep -i release

echo -e "\n=== Checking navigation entries for release-notes ==="
# Check mint.json content around navigation
if [ -f "./mint.json" ]; then
  grep -n "release-notes" ./mint.json
fi

Repository: Multiwoven/docs

Length of output: 1174

---

Create a release-notes landing page or update the tab URL to point to an existing page.

The tab entry references a non-existent landing page. The tab URL is set to "release-notes", but the repository contains only nested pages (release-notes/2025, release-notes/2024, release-notes/January_2025, etc.) with no root landing page file. This will result in a broken link when users click the Releases tab.

Choose one solution:

1. Create a release-notes.mdx file to serve as a landing page and index to the release notes
2. Update the tab URL to point directly to an existing page, such as "url": "release-notes/2025"

🤖 Prompt for AI Agents

In mint.json around lines 64–68 the "Releases" tab URL points to "release-notes"
which doesn't exist (only nested pages like release-notes/2025 are present); fix
by either 1) adding a root landing page file at docs/release-notes.mdx (or
whatever content dir is used) that lists/links the nested release-note pages and
commit it, or 2) change the tab entry's "url" value to an existing page such as
"release-notes/2025" (ensure the path matches your routing and run a local build
to verify the link works).