docs: MDCB 2.10.0 release notes

[JoanCamosTyk]

PR Type

Documentation

---

Description

• Add 2.9.1 MDCB release notes

• Document dependencies and upgrade links

• Publish new Docker download reference

• Mark overview latest version 2.9.1

---

Diagram Walkthrough

flowchart LR
  rn["MDCB 2.9.1 release notes"]
  deps["Dependencies, downloads, changelog"]
  ov["Release overview latest version"]
  rn -- "documents" --> deps
  rn -- "paired with" --> ov

Loading

File Walkthrough

Relevant files

Documentation

mdcb.mdx Add MDCB 2.9.1 release notes section                                          developer-support/release-notes/mdcb.mdx Add a new 2.9.1 release notes section Include release metadata, breaking changes, and deprecations Document supported third-party dependency versions Add upgrade link, Docker pull command, and changelog placeholder +50/-0    overview.mdx Update overview to latest MDCB release                                      developer-support/release-notes/overview.mdx Update MDCB latest version to 2.9.1 Change latestData.name to 2.9.1 Point Docker tag URL to v2.9.1 +3/-3

---

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
tyk	🟢 Ready	View Preview	Apr 2, 2026, 8:26 AM

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Placeholder date The new 2.9.1 release notes still contain an unreplaced placeholder for the release date. If this page is published as-is, users will see xx April 2026 instead of the actual release date. #### Release Date xx April 2026 Stale metadata latest was updated to 2.9.1, but latestData.date still looks like the previous release date. Any overview page or generated release listing that reads this metadata will show 2.9.1 with an incorrect February 2026 date. "name": "2.9.1", "date": "19/02/2026", "docker": "https://hub.docker.com/r/tykio/tyk-mdcb-docker/tags?page=1&name=v2.9.1" Empty changelog The new changelog section renders an accordion with an empty title and no content. On the published page this will show a blank expandable item, which makes the 2.9.1 changelog look incomplete. ##### Added <AccordionGroup> <Accordion title=''> </Accordion>

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Remove empty changelog accordion Rendering an Accordion with an empty title creates a blank interactive element and leaves the changelog section looking broken. If there are no items yet, replace the empty component with plain text until real entries are available. developer-support/release-notes/mdcb.mdx [62-68] -<AccordionGroup> +No user-facing additions are included in this release. -<Accordion title=''> - -</Accordion> - -</AccordionGroup> - Suggestion importance[1-10]: 6 __ Why: This is a valid usability/content issue: an empty Accordion with a blank title will render as broken or confusing UI in the changelog section. Replacing it with plain text until real entries exist is a reasonable improvement to mdcb.mdx.	Low
	Replace placeholder date Leaving xx in the published release date makes the release notes invalid and easy to misinterpret as unfinished content. Replace it with the finalized date before this becomes the latest linked release. developer-support/release-notes/mdcb.mdx [22] -#### Release Date xx April 2026 +#### Release Date 2 April 2026 Suggestion importance[1-10]: 4 __ Why: Leaving xx in #### Release Date xx April 2026 clearly looks like unfinished release-note content and should be fixed before publishing. Still, the suggested replacement 2 April 2026 is speculative because the PR does not provide the finalized day.	Low
Possible issue	Fix stale release metadata latestData.date still points to the previous release date even though this entry now advertises 2.9.1 as the latest version. This will surface incorrect metadata in the overview page and can mislead users or any logic that sorts/releases by date. developer-support/release-notes/overview.mdx [52-56] "latestData": { "name": "2.9.1", - "date": "19/02/2026", + "date": "02/04/2026", "docker": "https://hub.docker.com/r/tykio/tyk-mdcb-docker/tags?page=1&name=v2.9.1" } Suggestion importance[1-10]: 4 __ Why: The issue is real: latestData.date still shows the previous release's date while latest and latestData.name were updated to 2.9.1. However, the proposed 02/04/2026 value is not supported by the PR diff, so the suggestion is only partially grounded.	Low