fix(changelog): Include DocsChangelog component in serverless bundle

[sentry]

DESCRIBE YOUR PR

This PR resolves the "Module Not Found" error occurring on the /changelog.rsc route.

Problem:
The GET /changelog.rsc request was failing with a 500 "Module Not Found" error. The root cause was identified as the DocsChangelog React component not being included in the serverless bundle for the [[...path]] route.

While docs/changelog.mdx was correctly included in outputFileTracingIncludes, its imported component src/components/changelog/docsChangelog.tsx was not, leading to a runtime module resolution failure when the serverless function attempted to render the page.

Solution:
Added src/components/changelog/docsChangelog.tsx to the outputFileTracingIncludes array for the \[\[\.\.\.path\]\] route in next.config.ts. This ensures the necessary component is bundled with the serverless function, allowing the changelog page to render correctly.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview, Comment	Feb 5, 2026 1:05am
sentry-docs	Ready	Preview, Comment	Feb 5, 2026 1:05am

[nora-shap]

Hi! I triggered this pr, I'm testing an (unreleased) feature we're building.
Did you find this bug fix accurate and useful?

[nora-shap]

Closing this PR - incorrect approach

This PR attempted to fix the issue by using dynamic imports for API page components. However, this doesn't address the root cause and would lead to whack-a-mole fixes for every page that uses bundleMDX.

The Real Problem:
In commit a650c44 (#16232), we excluded node_modules/mdx-bundler/**/* from serverless bundles to avoid CJS/ESM issues with mdx-bundler/client. However:
✅ The CJS/ESM issue was already fixed by creating src/getMDXComponent.ts to replace mdx-bundler/client
❌ But we over-excluded - we excluded the entire mdx-bundler package, which broke bundleMDX (still needed at runtime for API pages and other dynamic MDX rendering)

My suggestion: remove the exclusion of node_modules/mdx-bundler/**/* from next.config.ts.