fix(ui): Move git_pr_number to number tags in explore constants#110040
Merged
runningcode merged 1 commit intomasterfrom Mar 6, 2026
Merged
fix(ui): Move git_pr_number to number tags in explore constants#110040runningcode merged 1 commit intomasterfrom
runningcode merged 1 commit intomasterfrom
Conversation
Move git_pr_number from SENTRY_PREPROD_STRING_TAGS to SENTRY_PREPROD_NUMBER_TAGS to match the backend where it is already in numeric_keys. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Frontend
nsdeschenes
approved these changes
Mar 6, 2026
chromy
approved these changes
Mar 6, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
git_pr_numberwas listed inSENTRY_PREPROD_STRING_TAGSbut PR numbers are integers. The backend already treats it as numeric (it's innumeric_keysinartifact_search.py). This moves it toSENTRY_PREPROD_NUMBER_TAGSso the explore view fetches and presents it correctly.Companion to #110033 which changes the field definition's
valueTypefromSTRINGtoINTEGER.