Uh oh!
There was an error while loading. Please reload this page.
chore(deps): bump @sentry/react from 10.56.0 to 10.57.0 - #1752
Merged
github-actions[bot] merged 1 commit intoJun 15, 2026
Conversation
ContributorAuthor
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
The latest updates on your projects. Learn more about Vercel for GitHub. |
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 10.56.0 to 10.57.0. - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@10.56.0...10.57.0) --- updated-dependencies: - dependency-name: "@sentry/react" dependency-version: 10.57.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabotBotforce-pushed
the
dependabot/npm_and_yarn/sentry/react-10.57.0
branch
from
June 15, 2026 08:10
8f1f0fe to
af0f0b2CompareUh oh!
There was an error while loading. Please reload this page.
Contributor
❌ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang added a commit
that referenced
this pull request
Jul 19, 2026
…erset (#1752) (#2672) Clicking a report/dashboard cell grouped by a `dateGranularity` date dimension ("2026-Q2") used to drill into a superset (the date dim was skipped, so the record list spanned every time bucket). It now scopes to the clicked bucket's half-open range via the framework's new `drillRanges` sidecar. - core: `buildDatasetDrillFilter` merges a per-row range as an ObjectQL operator object `{ [field]: { $gte, $lt } }` alongside equality dims. - plugin-report / plugin-dashboard: forward `drillRanges`; a date-ONLY report (no equality drill dim) is now drillable via the range alone. - app-shell: the "Open in list" escape hatch (`useOpenRecordList`) targets the ADR-0055 bare data surface (`/:object/data`) and serializes a range to `filter[field][gte|lt]`; `ObjectDataPage` parses those operators, renders a range as one chip, and removes both bounds together. New `drillUrlFilters` module owns write+read serialization (round-trip tested) so they can't drift. Companion to framework#3256. Claude-Session: https://claude.ai/code/session_01RCXBnmMQTwjmFkjtpEe11f Co-authored-by: Claude <noreply@anthropic.com>
This was referenced Aug 8, 2026
akarma-synetal pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Aug 10, 2026
…eryDataset (objectstack-ai#3813) (objectstack-ai#3824) The runtime half of the hand-picked-envelope family objectstack-ai#3613/objectstack-ai#3752 fixed on the type face. queryDataset rebuilds its result by picking keys off the REST payload one by one, and drillRanges was never in the list — so the analytics service's objectstack-ai#1752 date-range drill sidecar was dropped by the only real adapter in this repo, while five consumer sites were already reading it (DatasetWidget.tsx:471/:593, DatasetReportRenderer.tsx:316/:431/:855). The effect was a MISSING drill, not a degraded one. A dateGranularity dimension groups a span of records into one bucket, which equality filters cannot express, so service-analytics excludes date dims from dimensionFields/drillRawRows and sends a half-open [gte, lt) range per row instead (analytics-service.ts:807+). For a chart or report grouped only by time, drillRanges is therefore the only thing that can make canDrill = !!object && (drillDims.length > 0 || !!drillRanges?.length) true — dropped, the whole drill entry point disappeared. A mixed date + non-date grouping kept its drill but lost the time bound, so clicking June's bar opened every month (a superset). Neither side's tests could see it: the dashboard/report suites mock their own data source and feed drillRanges in directly, and the adapter's suite never asserted the key. The new tests mock the envelope the SERVER actually sends — bare (res.json, no success/data wrapper), carrying sql, and for a date-only grouping carrying object + drillRanges and NO dimensionFields/drillRawRows — then assert the key arrives verbatim and row-aligned, that the consumers' own canDrill predicate is true, and that the shared buildDatasetDrillFilter scopes the list to the clicked bucket (both halves for a mixed grouping). The entry type is @object-ui/core's DatasetDrillRange BY REFERENCE, not a local { field, gte, lt } copy: it is the single in-repo declaration of the shape (what buildDatasetDrillFilter accepts and what both renderers type their state with) and @objectstack/spec does not own it yet, so a restatement would be a third dialect. drillRawTotals (objectstack-ai#3214) is deliberately NOT added: zero consumers in this repo, so passing it through would add a declared-but-unexercised key with no user-facing effect. Filed separately as a finding. Claude-Session: https://claude.ai/code/session_01GTRjn8xBqp75dk7kFupVRt Co-authored-by: Claude <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps @sentry/react from 10.56.0 to 10.57.0.
Release notes
Sourced from @sentry/react's releases.
... (truncated)
Changelog
Sourced from @sentry/react's changelog.
... (truncated)
Commits
950cf97release: 10.57.055f9343Merge pull request #21369 from getsentry/prepare-release/10.57.088d9d30meta(changelog): Update changelog for 10.57.003ffd25fix(cloudflare): Don't track negatively sampled spans (#21367)7c19eadref(node): Streamline sql-common (#21360)95df562feat(hono): Filter noisy transactions (faviconetc) (#21365)92eb5d2feat(deps): Bump hono from 4.12.18 to 4.12.21 (#21341)c6f790bfix(node): Prevent PostgresJs integration from emitting duplicate spans per q...d645349ref(node): Streamline lru-memoizer instrumentation (#21350)4293015feat(deps): Bump@types/aws-lambdafrom 8.10.150 to 8.10.161 (#21105)