fix(api): Update List Seer AI Models to reflect that it is regional#104530
Merged
fix(api): Update List Seer AI Models to reflect that it is regional#104530
Conversation
github-actions
bot
added
Scope: Frontend
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 |
sehr-m
removed
the
Scope: Frontend
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #104530 +/- ##
===========================================
+ Coverage 73.47% 80.51% +7.04%
===========================================
Files 9348 9352 +4
Lines 400237 400521 +284
Branches 25700 25700
===========================================
+ Hits 294067 322490 +28423
+ Misses 105702 77563 -28139
Partials 468 468 |
sergical
approved these changes
Dec 8, 2025
Member
sergical
left a comment
sergical
left a comment
There was a problem hiding this comment.
looks good from the docs side of things
JoshFerge
reviewed
Dec 8, 2025
Member
JoshFerge
left a comment
JoshFerge
left a comment
There was a problem hiding this comment.
will our API docs site render the server information right now?
ryan953
pushed a commit
that referenced
this pull request
Dec 9, 2025
…104530) <!-- Describe your PR here. --> The "List Seer AI Models" api reference did not specify a regional url. Historically, these were added in manually, but we have since switched to spectacular to create our json. I have added a servers attribute to the base api and a catch that will add the attribute to the method info if servers are specified. The watch command to test also had a legacy error that I fixed to properly see the changes. (This was moved to a separate PR as a frontend change) To test follow these instructions: https://develop.sentry.dev/backend/api/public/#building-and-testing-locally <!-- Sentry employees and contractors can delete or ignore the following. --> ### 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "List Seer AI Models" api reference did not specify a regional url. Historically, these were added in manually, but we have since switched to spectacular to create our json. I have added a servers attribute to the base api and a catch that will add the attribute to the method info if servers are specified.
The watch command to test also had a legacy error that I fixed to properly see the changes. (This was moved to a separate PR as a frontend change)
To test follow these instructions: https://develop.sentry.dev/backend/api/public/#building-and-testing-locally
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.