[mydea]

DESCRIBE YOUR PR

Items in the interactive JavaScript v11 migration guide (includes/migration/javascript-v11/*.mdx) can only be scoped with a frameworks allowlist (or all). There's no way to show an item everywhere except for a few frameworks.

• Add an optional excludeFrameworks frontmatter field to migration guide items, filtered in src/components/migrationGuide/index.tsx.
• Use it on the profiling-legacy-options item for bun, cloudflare, and deno. These SDKs don't support profiling (the Profiling page is hidden for them), so the item was irrelevant there, and its link to /profiling/ returned 404 on:
  • /platforms/javascript/guides/bun/migration/v10-to-v11/interactive/
  • /platforms/javascript/guides/cloudflare/migration/v10-to-v11/interactive/
  • /platforms/javascript/guides/deno/migration/v10-to-v11/interactive/

Example:

frameworks: all
excludeFrameworks: [bun, cloudflare, deno]

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: 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 supplied a deadline.

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

---

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Sep 30, 2026 12:10pm UTC
sentry-docs	Ready	Preview	Sep 30, 2026 12:10pm UTC

[cursor]

The plan checks whether excluded frameworks omit one checklist item. It also checks errors and page-load counts on the interactive migration pages. An issue escalates when those pages error, fail to load, or hide the item on frameworks that should still show it.

Services: sentry-docs, develop-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The interactive JavaScript v11 migration checklist hides the profiling-legacy-options item on bun, cloudflare, and deno. Other frameworks still show that item. The new excludeFrameworks filter in MigrationGuide applies this hide. The change is live after sentry-docs deploys. develop-docs also ships the shared component. The checklist pages exist only on docs.sentry.io.

Risk

A bad filter can hide the item on every framework, or drop the whole checklist. A throw in the new excludeFrameworks.includes check can fail render of every interactive v11 page. Those pages are static. A render throw can 404 or 500 the page. The component lives in shared src/, so a compile failure also fails the develop-docs build. Users on bun, cloudflare, and deno could keep a false action if the hide does not apply.

Intended effect

After deploy, the bun, cloudflare, and deno interactive pages must omit the item with id="profiling-legacy-options". The Next.js interactive page must still include that item. absent looks like this: the excluded pages still contain that heading, while page loads continue.

Production does not ship excludeFrameworks yet. The item is in the checklist for every framework that uses frameworks: all.

Signal	Baseline	Window	Rule	Source
HTML of excluded-framework interactive pages	Item present	2026-09-30T12:12:27Z, pre-change production	After deploy the item must be absent	GET https://docs.sentry.io/platforms/javascript/guides/bun/migration/v10-to-v11/interactive/, the cloudflare URL, and the deno URL. Look for id="profiling-legacy-options" or the heading `profilesSampleRate` and `profilesSampler` were removed.
HTML of the Next.js interactive page	Item present	2026-09-30T12:12:27Z, pre-change production	After deploy the item must stay present	GET https://docs.sentry.io/platforms/javascript/guides/nextjs/migration/v10-to-v11/interactive/ and look for the same id.

Regression watch

A throw or empty checklist on this path is the first user-visible failure. Watch errors and load volume on the interactive pages. Also watch that sibling framework pages still show the item.

Signal	Baseline	Window	Rule	Source
Error count on interactive migration URLs	0 events	2026-09-29T12:12:27Z to 2026-09-30T12:12:27Z	Hold at 0. Any rise is a regression.	Sentry org sentry, project docs. Dataset errors. Query environment:production url:*v10-to-v11/interactive*.
Error count with MigrationGuide on the stack	0 events	2026-09-23T12:12:27Z to 2026-09-30T12:12:27Z	Hold at 0.	Sentry org sentry, project docs. Dataset errors. Query environment:production AND (stack:*migrationGuide* OR stack:*MigrationGuide* OR message:*excludeFrameworks*).
docs.page.load on interactive paths	85 counts in 24h. 1054 counts in 7d. About 85-151 counts per day.	24h: 2026-09-29T12:12:27Z to 2026-09-30T12:12:27Z. 7d: 2026-09-23T12:12:27Z to 2026-09-30T12:12:27Z.	Hold in the 85-151 counts per 24h band. A fall toward 0 means the pages failed to render.	Sentry org sentry, project docs. Dataset metrics. Query metric.name:docs.page.load AND path:*v10-to-v11/interactive*.
HTML of sibling interactive pages	Item present on Next.js. Bare JavaScript uses no guide name, so the exclude check does not run.	2026-09-30T12:12:27Z, pre-change production	Next.js and other non-excluded guides must still show profiling-legacy-options. Other checklist items must still render.	GET the Next.js URL above and https://docs.sentry.io/platforms/javascript/migration/v10-to-v11/interactive/.

Transaction names on this site are /:path*?. Do not filter errors by transaction *interactive*. Use the url field.

Not observable

No per-item view or click metric exists, so telemetry cannot prove the hide by itself. Fetch the page HTML for intended effect. Pageload spans did not match http.target:*interactive*. Use docs.page.load with the path attribute instead. This session did not parse live HTML for the item id. The present-item baseline comes from unreleased code, not from a parsed production snapshot. develop-docs ships the shared component but has no interactive v11 pages. Runtime effect on develop.sentry.dev is not measurable.

[sentry]

Bug: The excludeFrameworks field from YAML is assumed to be an array but lacks runtime validation. A non-array value will cause a TypeError and crash the build process.
_{Severity: MEDIUM}

Suggested Fix

Add a runtime check to validate that excludeFrameworks is an array before attempting to call array methods on it. Use Array.isArray() to guard against incorrect types and either filter out invalid values or throw a more informative error to the author.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/components/migrationGuide/index.tsx#L61

Potential issue: The `excludeFrameworks` field, parsed from YAML frontmatter, is
type-asserted as `string[]` without any runtime validation. The code uses a nullish
coalescing operator (`?? []`) which only handles `null` or `undefined` cases. If an
author provides a non-array, non-string value in the YAML (e.g., a boolean, number, or
object), the subsequent call to `.includes()` on this value will raise a `TypeError`.
This will cause the application to crash during the build or deployment process,
preventing site updates.

_{Did we get this right? 👍 / 👎 to inform future reviews.}