[pull] master from getsentry:master#1609
Merged
pull[bot] merged 13 commits intoKingDEV95:masterfrom Jan 8, 2026
Merged
Conversation
Found an issue with the auto-replace search key functionality of the search query builder with aggregate functions. I made the move to utilize the `parseQuery` function that is setup in the query builder context. This also means that whenever we parse queries in the query builder state it will use that configured parser with all of the options passed through. Ticket: EXP-649
…volume_projects (#105226)
These have been fully rolled out, and will be removed from the FE as well once these are merged.
Make prompt more structured to improve response quality. Include source_root to make it work for multi-project repos.
Change max width from `fit-content` to `130px` so that it doesn't expand incorrectly.
Update to use options-automator like [here](https://github.com/getsentry/sentry-options-automator/pull/6079/files) instead of hardcoded values so we can have shorter deploy/test cycles.
Add new organization-level feature flag to control OTLP span processing via the Span V2 pipeline in Relay.
Applying a legend alias in the widget builder wasn't working for metrics widgets. There were two steps to making this work: 1. Stop overwriting `timeSeries.yAxis` because once it was overridden, it would alter the data for subsequent rendering when applying the alias 2. In the `transformSeries` function, update the label formatter to add the correct separators and alias prefix The logic follows what's provided for other previous datasets e.g. - If you have a single aggregate, no groupings -> the alias prefixes the aggregate - Single aggregate, groupings -> the alias prefixes the group labels - Multiple aggregates, no groupings -> alias prefixes all aggregates - Multiple aggregates, multiple groupings -> alias prefixes all of the groups, which also has an aggregate suffix (e.g. `My Alias > iOS : avg(latency)`) When you have multiple filters, that's when the alias prefixes can differ because each series in the filter results gets aliased
github-actions
bot
added
Scope: Frontend
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.
7 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )