Add release notes for v2.14.2 and v2.14.3

[jlowin]

Cherry-pick of #2851 to main for 3.x documentation.

Adds documentation entries for both 2.x releases to docs/updates.mdx and docs/changelog.mdx.

[coderabbitai]

Walkthrough

This pull request adds two new release documentation entries to the FastMCP changelog and release notes. Version 2.14.3 (Time After Timeout) and version 2.14.2 (Port Authority) are appended to docs/changelog.mdx and docs/updates.mdx with their respective descriptions, enhancement details, fixes, and documentation notes. The existing release entries remain in the documents but are positioned lower in document order. These are purely documentation additions with no code or logic modifications.

Possibly related PRs

• Add changelog entries for v2.13.1 through v2.14.1 #2724: Modifies the same changelog and release notes documentation files by adding earlier version entries (v2.13.1–v2.14.1).
• Add changelog entries for v2.13.1 through v2.14.1 #2725: Updates the same documentation files with release entries for the earlier version range (v2.13.1–v2.14.1).

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description identifies the PR as a cherry-pick and explains what was added, but does not follow the required template with Contributors and Review Checklists.	Complete the required checklist sections from the template: mark off items in the Contributors Checklist (issue reference, workflow, testing, documentation) and Review Checklist (self-review, readiness) to fully comply with repository standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add release notes for v2.14.2 and v2.14.3' accurately and concisely summarizes the main change of adding documentation entries for two new releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/changelog.mdx (1)

1-57: Pipeline failure: File exceeds line count limit.

The static analysis hook loq reports that this file has 2,280 lines, exceeding the allowed limit of 2,228 lines. This is blocking the CI pipeline.

Consider one of these approaches to resolve:

1. Archive older changelog entries (e.g., pre-2.0 releases) to a separate file like changelog-archive.mdx
2. Condense or summarize very old entries
3. Request an increase to the line limit if justified

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b18db2 and 07d3048.

📒 Files selected for processing (2)

• docs/changelog.mdx
• docs/updates.mdx

🧰 Additional context used

📓 Path-based instructions (1)

docs/**/*.mdx

📄 CodeRabbit inference engine (docs/.cursor/rules/mintlify.mdc)

docs/**/*.mdx: Use clear, direct language appropriate for technical audiences
Write in second person ('you') for instructions and procedures in MDX documentation
Use active voice over passive voice in MDX technical documentation
Employ present tense for current states and future tense for outcomes in MDX documentation
Maintain consistent terminology throughout all MDX documentation
Keep sentences concise while providing necessary context in MDX documentation
Use parallel structure in lists, headings, and procedures in MDX documentation
Lead with the most important information using inverted pyramid structure in MDX documentation
Use progressive disclosure in MDX documentation: present basic concepts before advanced ones
Break complex procedures into numbered steps in MDX documentation
Include prerequisites and context before instructions in MDX documentation
Provide expected outcomes for each major step in MDX documentation
End sections with next steps or related information in MDX documentation
Use descriptive, keyword-rich headings for navigation and SEO in MDX documentation
Focus on user goals and outcomes rather than system features in MDX documentation
Anticipate common questions and address them proactively in MDX documentation
Include troubleshooting for likely failure points in MDX documentation
Provide multiple pathways (beginner vs advanced) but offer an opinionated path to avoid overwhelming users in MDX documentation
Always include complete, runnable code examples that users can copy and execute in MDX documentation
Show proper error handling and edge case management in MDX code examples
Use realistic data instead of placeholder values in MDX code examples
Include expected outputs and results for verification in MDX code examples
Test all code examples thoroughly before publishing in MDX documentation
Specify language and include filename when relevant in MDX code examples
Add explanatory comments for complex logic in MDX code examples
Document all API...

Files:

• docs/updates.mdx
• docs/changelog.mdx

🪛 GitHub Actions: Run static analysis

docs/changelog.mdx

[error] 1-1: loq hook failed: 2_280 > 2_228 in docs/changelog.mdx (1 violation). Process completed with exit code 1.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Run tests with lowest-direct dependencies
• GitHub Check: Run tests: Python 3.13 on ubuntu-latest
• GitHub Check: Run tests: Python 3.10 on ubuntu-latest
• GitHub Check: Run tests: Python 3.10 on windows-latest

🔇 Additional comments (3)

docs/changelog.mdx (1)

7-26: LGTM!

The v2.14.3 entry is well-structured, follows the established changelog format, and includes appropriate sections for enhancements, fixes, and the full changelog link.

docs/updates.mdx (2)

8-20: LGTM!

The v2.14.3 update entry is well-formatted, follows the established pattern with the <Update> and <Card> components, and provides a clear, concise summary of the release highlights.

---

22-34: LGTM!

The v2.14.2 update entry is properly structured with clear highlight sections and follows the established documentation pattern.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Clarify unclear changelog entry description.

The description "conference to 2.x branch" appears incomplete or unclear. Consider revising to clarify what this change does (e.g., "Merge conference changes to 2.x branch" or similar).