Repository navigation
ref(flags): Remove organizations:autofix-browser-notifications registration - #129456
cursor[bot] wants to merge 1 commit into
Conversation
…ration GA in the automator since #9026 (2026-08-03). Reads removed in #129455, flagpole value in getsentry/sentry-options-automator#10417. Co-authored-by: charlie.luo <charlie.luo@sentry.io>
There was a problem hiding this comment.
@getsentry/machine-learning-ai — last of three for organizations:autofix-browser-notifications, opened by the stale-flag-cleanup automation. @ryan953 is requested as reviewer since he created and rolled out the flag.
Merge this one last: #129455 (frontend reads) → getsentry/sentry-options-automator#10417 (flagpole value) → this PR. The flag has no backend readers, so green CI here does not depend on #129455 — the ordering exists so the flagpole block is never orphaned and so api_expose keeps emitting the flag while the UI still reads it.
The flagpole block carried a Disable for sandbox org segment above its GA segment; #129455 preserves that as !isDemoModeActive() and explains why. Worth reading that PR's discussion before merging this one.
CI is green apart from getsentry dispatch, which gates on the author having write permission and always fails for cursor[bot] — a collaborator needs to add the Trigger: getsentry tests label.
Sent by Cursor Automation: Feature flag cleanup


Remove the
temporary.pyregistration fororganizations:autofix-browser-notifications. The flag was rolled out to GA in the automator in getsentry/sentry-options-automator#9026 on 8/3, and hasn't been touched since.Last of three, merge in order:
The flag has no backend readers, so this does not depend on #129455 for green CI; the ordering is so the flagpole block is never orphaned and
api_exposekeeps emitting the flag while the UI still reads it.The
Disable for sandbox orgsegment the flagpole block carried is preserved in code as!isDemoModeActive()by #129455.