Add changelog entries for v2.13.1 through v2.14.1

[jlowin]

Updates docs/changelog.mdx and docs/updates.mdx with release notes for five releases that were missing:

• v2.14.1 (Dec 15): Sampling with tools, AnthropicSamplingHandler
• v2.14.0 (Dec 11): Background tasks (SEP-1686), OpenAPI parser promotion
• v2.13.3 (Dec 3): MCP SDK pin below 1.23
• v2.13.2 (Dec 1): Discord OAuth, token refresh fixes
• v2.13.1 (Nov 15): Meta parameters for ToolResult, OCI/Supabase auth

[coderabbitai]

Walkthrough

This pull request updates two documentation files with new release information. The docs/changelog.mdx file receives an expanded version history with entries spanning from v2.14.1 through v0.1.0, documenting features, enhancements, fixes, and contributor notes for each release. The docs/updates.mdx file adds new release entry blocks for versions 2.14.1, 2.14.0, 2.13.3, 2.13.2, and 2.13.1, each containing Card metadata and release notes. These are purely documentation additions with no changes to code functionality or exported entities.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides clear details about what releases were added and their key features, but is missing the required Contributors and Review checklists from the template.	Complete the provided template by adding the Contributors Checklist and Review Checklist sections with appropriate checkboxes marked, particularly noting the related issue number.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and directly summarizes the main change: adding changelog entries for versions v2.13.1 through v2.14.1, which aligns with the file modifications to docs/changelog.mdx and docs/updates.mdx.
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/changelog-updates-2.13.1-to-2.14.1

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ee9ee77 and efe85ad.

📒 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/changelog.mdx
• docs/updates.mdx

🧠 Learnings (1)

📚 Learning: 2025-12-01T15:48:05.095Z

Learnt from: jlowin
Repo: jlowin/fastmcp PR: 0
File: :0-0
Timestamp: 2025-12-01T15:48:05.095Z
Learning: PR #2505 in fastmcp adds NEW functionality to get_access_token(): it now first checks request.scope["user"] for the token (which never existed before), then falls back to _sdk_get_access_token() (the only thing the original code did). This is not a reversal of order but entirely new functionality to fix stale token issues.

Applied to files:

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

⏰ 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: 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
• GitHub Check: Run tests with lowest-direct dependencies

🔇 Additional comments (2)

docs/changelog.mdx (1)

7-171: LGTM! Well-structured changelog additions.

The five new release entries (v2.14.1 through v2.13.1) are well-organized and follow the established changelog format consistently. Each entry includes:

• Proper Update component structure with clear labels and dates
• Descriptive release titles and summaries
• Well-organized sections (New Features, Enhancements, Fixes, Docs, etc.)
• Properly formatted links to PRs and contributors
• Consistent use of emojis for visual hierarchy
• Full changelog comparison links

The content is clear, uses active language appropriately, and maintains consistent terminology throughout. Dates are consistent with the corresponding entries in docs/updates.mdx.

docs/updates.mdx (1)

8-78: LGTM! Excellent user-facing release summaries.

The five new release entries follow the established pattern perfectly. Each entry:

• Uses the Update component with clear labels and dates that match docs/changelog.mdx
• Contains a properly structured Card component with title, href, and cta properties
• Provides concise, user-friendly summaries that highlight key features
• Uses emojis effectively for visual hierarchy and quick scanning
• Maintains consistent terminology and style

The content is clear, direct, and focuses on user-relevant information without overwhelming detail. The summaries effectively communicate the value of each release while linking to full release notes for those who want more information.

---

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.}

[marvin-context-protocol]

Test Failure Analysis

Summary: The Windows Python 3.10 test job failed with exit code 1 on this documentation-only PR. This appears to be a transient failure related to known Windows-specific test infrastructure issues.

Root Cause: Based on investigation of recent repository history and related issues, this failure is likely caused by one of these known Windows testing problems:

1. pytest-xdist worker crashes - Issue Marvin Test Failure fails to edit existing comment #2559 documents that Windows has known flaky issues with pytest-xdist parallel test execution, causing worker crashes unrelated to code changes
2. Stdio subprocess instability - PRs Skip test_multi_client on Windows #2714 and Enable parallel tests on Windows #2715 addressed similar Windows test timeouts by skipping stdio subprocess tests on Windows (already fixed in main)
3. Platform-specific test flakiness - The test suite runs with --numprocesses auto --maxprocesses 4 on Windows, which can trigger race conditions

Current Status: ✅ Tests are now passing on main branch. The most recent workflow runs show all checks succeeding, confirming this was a transient failure.

Why This Happened: The workflow configuration runs tests on all pull requests (even docs-only changes) because test checks are required for merging. While pushes to main use path filters to skip tests for docs changes, PRs don't have this optimization.

Evidence & Context

Check Run Results for this commit:

• ✅ Python 3.13 on ubuntu-latest: Success
• ✅ Python 3.10 on ubuntu-latest: Success
• ❌ Python 3.10 on windows-latest: Failed (exit code 1)
• ✅ Run integration tests: Success
• ✅ Run tests with lowest-direct dependencies: Success

Recent Windows Test Fixes:

• PR Skip test_multi_client on Windows #2714: "Skip test_multi_client on Windows" - Added file-level skip for test_mcp_config.py due to stdio subprocess timeouts
• PR Enable parallel tests on Windows #2715: "Enable parallel tests on Windows" - Re-enabled parallel execution after problematic tests were skipped

Known Issues:

• Issue Marvin Test Failure fails to edit existing comment #2559: Marvin Test Failure documents Windows pytest-xdist worker crashes described as "known flaky Windows-specific issues"
• Windows CI has recurring issues with stdio subprocess tests timing out

Recommended Actions

Since the PR is already merged and tests are passing on main, no action is required. However, to prevent similar noise in the future, consider:

1. Add path filters to pull_request trigger in .github/workflows/run-tests.yml to skip tests for docs-only PRs (similar to the push trigger):

   pull_request:
     paths:
       - "src/**"
       - "tests/**"
       - "uv.lock"
       - "pyproject.toml"
       - ".github/workflows/**"

2. Continue monitoring Windows test stability - Track if worker crashes persist

3. Document Windows testing limitations - Add notes about known flakiness to contributor docs

---

Analysis completed by Marvin test failure triage bot. This was a transient Windows infrastructure issue, not a problem with the PR changes.