Skip to content

ref(flags): Remove organizations:tracemetrics-pii-scrubbing-ui gate (frontend) - #127147

Open
cursor[bot] wants to merge 1 commit into
masterfrom
claude-rm-tracemetrics-pii-scrubbing-ui
Open

cursor[bot] wants to merge 1 commit into
masterfrom
claude-rm-tracemetrics-pii-scrubbing-ui

Conversation

@cursor

@cursor cursor Bot commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Remove organizations:tracemetrics-pii-scrubbing-ui. This flag was fully rolled out in the automator in PR #7574 on 4/28/26 (segment with no conditions at 100% rollout), and hasn't been touched since.

The only reader was canUseMetricsPiiScrubbingUI in static/app/views/explore/metrics/metricsFlags.tsx, added in #113078. The predicate still has two callers in static/app/views/settings/components/dataScrubbing/, so its body is collapsed to the surviving tracemetrics-enabled gate rather than deleted — same shape as #115018, which graduated canUseMetricsAlertsUI in this file.

First of three PRs (reads -> automator value -> registration):

  1. this PR
  2. sentry-options-automator: remove the flagpole value
  3. sentry: remove the temporary.py registration

Verified locally: pnpm run typecheck clean, 353 tests pass across dataScrubbing/ and explore/metrics/, oxlint + oxfmt clean.

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.

Open in Web View Automation 

… (frontend)

The flag has been fully rolled out (segment with no conditions at 100%
rollout) in sentry-options-automator since #7574 (2026-04-28), so
collapse the predicate to the surviving `tracemetrics-enabled` gate.

Co-authored-by: charlie.luo <charlie.luo@sentry.io>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 10, 2026
@cursor
cursor Bot marked this pull request as ready for review October 10, 2026 20:40
@cursor
cursor Bot requested a review from a team as a code owner October 10, 2026 20:40

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@getsentry/data-browsing @getsentry/explore — review please. data-browsing is the owner.team on the flagpole entry; @getsentry/explore owns /static/app/views/explore/ in CODEOWNERS.

Merge order — this is PR 1 of 3:

  1. this PR (frontend gate)
  2. getsentry/sentry-options-automator#10134 (flagpole value)
  3. #127148 (temporary.py registration) — merge last, after #10134 has deployed everywhere

CI is green apart from getsentry dispatch, which fails on every PR this bot opens because the check gates on the author having write permission. A collaborator needs to add the Trigger: getsentry tests label if you want those to run.

Note for reviewers: canUseMetricsPiiScrubbingUI is kept rather than deleted because it still has two callers in static/app/views/settings/components/dataScrubbing/. That matches #115018, which collapsed canUseMetricsAlertsUI in this same file. Happy to inline it at the call sites instead if you'd prefer.

View PR

Open in Web View Automation 

Sent by Cursor Automation: Feature flag cleanup

This branch was successfully deployed

1 active deployment
Preview — 9a1e3045 Deployed Oct 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant