Skip to content

chore(api): Remove single trace summary backend endpoint#113666

Merged
nsdeschenes merged 4 commits intomasterfrom
nd/ENG-7415/chore-trace-summaries-remove-from-api
Apr 22, 2026
Merged

chore(api): Remove single trace summary backend endpoint#113666
nsdeschenes merged 4 commits intomasterfrom
nd/ENG-7415/chore-trace-summaries-remove-from-api

Conversation

@nsdeschenes
Copy link
Copy Markdown
Contributor

@nsdeschenes nsdeschenes commented Apr 22, 2026

Remove the backend API surface for single trace summaries.

This retires the temporary single-trace-summary backend path instead of making it always on. The PR removes the feature registration, unregisters the organization trace-summary endpoint, and deletes the dedicated Seer helper and backend tests that only existed for that API.

Frontend cleanup is intentionally left out of this PR, it's removal is in this PR: #113663

nsdeschenes and others added 2 commits April 22, 2026 11:09
Remove the public trace summary API entry points from the backend.

Drop the temporary feature registration and unregister the organization
trace-summary route so clients no longer discover or call the retired
endpoint through the API surface.

Co-Authored-By: Codex <codex@openai.com>
Remove the dedicated Seer trace summary implementation and its tests
now that the API route has been retired.

This drops backend-only code that no longer has any remaining callers and
keeps the Seer package free of dead endpoint helpers.

Co-Authored-By: Codex <codex@openai.com>
@linear-code
Copy link
Copy Markdown

linear-code Bot commented Apr 22, 2026

ENG-7415 Remove from API

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 22, 2026
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 22, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@nsdeschenes nsdeschenes marked this pull request as ready for review April 22, 2026 14:15
@nsdeschenes nsdeschenes requested review from a team as code owners April 22, 2026 14:15
@nsdeschenes nsdeschenes merged commit fef0b57 into master Apr 22, 2026
109 of 112 checks passed
@nsdeschenes nsdeschenes deleted the nd/ENG-7415/chore-trace-summaries-remove-from-api branch April 22, 2026 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants