chore: upgrade Mintlify from v4.0.436 to v4.2.87

[devin-ai-integration]

What does this PR do?

Upgrades Mintlify documentation framework from version 4.0.436 to the latest stable version 4.2.87 in the GitHub Actions workflow. This ensures the documentation build process uses the most recent version with latest features and security updates.

The change affects only the CI/CD pipeline - no application code or documentation content was modified.

Testing Performed

• ✅ Local build verification: Tested mintlify dev locally with version 4.2.87 - documentation builds and renders correctly
• ✅ Configuration compatibility: Verified existing mint.json configuration works with new version
• ✅ Type checking: Ran yarn type-check:ci --force across entire monorepo - no type errors introduced
• ✅ Migration compatibility: Tested both mint.json and docs.json configurations work (future-proofing)

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - This is an internal build tool upgrade with no user-facing changes.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

The primary test is ensuring the documentation build workflow still passes in CI:

1. Monitor CI checks: Verify the "Build Docs" workflow completes successfully
2. Check documentation site: Ensure all documentation pages still render correctly
3. Verify no broken links: Confirm navigation and cross-references work as expected

Expected outcome: Documentation builds successfully and renders identically to the previous version.

⚠️ Review Notes

• Version jump: This upgrades from 4.0.436 to 4.2.87 (significant version increase)
• Changelog unavailable: Official Mintlify changelog was inaccessible during development
• Potential breaking changes: While local testing passed, monitor CI for any unexpected issues

---

Link to Devin run: https://app.devin.ai/sessions/5b6ec5e768c94ec189edce3881a72afd
Requested by: ali@cal.com

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbit review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
cal	Ignored			Aug 29, 2025 9:15am
cal-eu	Ignored			Aug 29, 2025 9:15am

[github-actions]

E2E results are ready!

• Workflow #74284.1 latest results