Skip to content

fix(seer): Send billed feature labels in the Seer credit check - #131168

Draft
wedamija wants to merge 2 commits into
masterfrom
danf/seer-credit-check-labels
Draft

wedamija wants to merge 2 commits into
masterfrom
danf/seer-credit-check-labels

Conversation

@wedamija

@wedamija wedamija commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Part of the Seer token-based billing work. Before a Seer operation starts we ask billing whether the org has enough credits for it.

We were sending autofix and explorer as the feature, but billing renamed its labels and doesn't bill those two anymore. Anything it doesn't bill gets let through, so the check always passed. This sends the new labels.

Refs CW-2314

@linear-code

linear-code Bot commented Nov 14, 2026

Copy link
Copy Markdown

CW-2314

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 14, 2026
@github-actions

Copy link
Copy Markdown
Contributor

decision-model-linter

api

src/sentry/seer/endpoints/group_ai_autofix.py

  • warn makesExistingInputStricter = TRUE (0.85): Rejecting input an endpoint accepted before, or changing a field's default, breaks existing callers, and the API spec often doesn't show it. Make the change backward compatible (keep the field optional, accept the old values, or keep the old default), or treat it as a breaking change and coordinate it.

decision-model-linter: 36 calls on 9 files, 87,313 input tokens, $0.0037, model typesafe/jev-1.13-20260917

This branch has not been deployed

No deployments
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant