Skip to content

Added Release note for customer reference #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nagstler wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added Release note for customer reference #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions mint.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,10 @@
{
"name": "Developers",
"url": "api-reference"
},
{
"name": "Releases",
"url": "release-notes"
}
Comment on lines +64 to 68
Copy link

@coderabbitai coderabbitai bot Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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).

],
"anchors": [],
Expand Down