[dependabot]

Bumps the minor-and-patch group in /packages/browseros-agent with 27 updates:

Package	From	To
@aws-sdk/client-s3	3.1073.0	3.1075.0
@biomejs/biome	2.5.0	2.5.1
fallow	2.101.0	2.102.0
@posthog/react	1.10.2	1.10.3
@ricky0123/vad-web	0.0.17	0.0.30
@sentry/react	10.59.0	10.61.0
@tanstack/query-async-storage-persister	5.101.0	5.101.1
@tanstack/react-query	5.101.0	5.101.1
@tanstack/react-query-persist-client	5.101.0	5.101.1
@xyflow/react	12.11.0	12.11.1
es-toolkit	1.48.1	1.49.0
hono	4.12.26	4.12.27
motion	12.40.0	12.42.0
nanoid	5.1.15	5.1.16
posthog-js	1.391.7	1.393.5
swr	2.4.1	2.4.2
@types/chrome	0.1.43	0.2.0
wxt	0.20.26	0.20.27
@rive-app/react-webgl2	4.29.1	4.29.3
@anthropic-ai/claude-agent-sdk	0.2.141	0.3.193
@hono/mcp	0.2.5	0.3.0
@sentry/bun	10.59.0	10.61.0
acpx	0.10.0	0.11.2
core-js	3.45.1	3.49.0
partysocket	1.2.0	1.3.0
zod-from-json-schema	0.1.0	0.5.3
puppeteer	25.1.0	25.2.1

Updates @aws-sdk/client-s3 from 3.1073.0 to 3.1075.0

Release notes

Sourced from @​aws-sdk/client-s3's releases.

v3.1075.0

3.1075.0(2026-06-23)

New Features

• client-kafka: Amazon MSK Replicator now supports mTLS authentication when connecting to external Apache Kafka clusters, enabling customers to replicate data from clusters that require mutual TLS for client authentication. This capability is supported when replicating to Amazon MSK Express brokers. (005f9529)

---

For list of updated packages, view updated-packages.md in assets-3.1075.0.zip

v3.1074.0

3.1074.0(2026-06-22)

Chores

• xml-builder:
  • move testing devDeps to root, remove unused nodable dep (#8118) (ed82880d)
  • parse XML internally (#7863) (74d0a071)

Documentation Changes

• typo in contributing.md (#8116) (87ff33d3)

New Features

• clients: update client endpoints as of 2026-06-22 (3a55a333)
• client-cloudwatch-logs: CloudWatch Logs Updates - New APIs introduced to support syslog ingestion to a log group. For more information, see CloudWatch Logs API documentation. (01a3b513)
• client-bedrock-agentcore: Adds an optional extractionMode field to CreateEvent. SKIP retains the event in short-term memory but excludes it from long-term memory extraction. (749753ad)
• client-omics: Adds support for scratch ephemeral storage mounted at tmp (331e3023)
• client-application-signals: Application Signals now supports dynamic instrumentation and Service Events telemetry. Add instrumentation at runtime without restarts, and use fine-grained profiling data to quickly pinpoint latency and error root causes. (f93b1c03)
• client-mediaconnect: AWS MediaConnect now supports Content Quality Analysis for Router Inputs, enabling detection of black frames, frozen frames, and silent audio with configurable thresholds. (05054853)
• client-lambda-core: Initial release of the AWS Lambda Core SDK with APIs to create, manage, and tag network connectors that enable Lambda compute resources to access private resources in your Amazon VPC. (e35cdab8)
• client-lambda: Add support for tagging Network Connector resources in AWS Lambda. (fbfc4078)
• client-guardduty: Added AI-powered investigations that automatically analyze security findings, correlate related activity, and produce structured summaries with risk assessment, confidence scoring, MITRE technique classification, and actionable next steps. (83c29839)
• client-lambda-microvms: Lambda MicroVMs GA launch. Lambda MicroVMs enable isolated and highly responsive execution of user-supplied or LLM-generated code. (5519a7e2)
• client-kafka: Amazon MSK Replicator now supports mTLS authentication when connecting to external Apache Kafka clusters, enabling customers to replicate data from clusters that require mutual TLS for client authentication. This capability is supported when replicating to Amazon MSK Express brokers. (ce7d1bf5)
• client-quicksight: Updated the Amazon Quick Spaces API to remove unsupported SPACE and ARTIFACT values from the SpaceQuickSightResourceType enum. (e1b325d4)
• client-ec2: This release adds support for AMI Watermark and Allowed AMIs integration (d1698bed)
• client-direct-connect: Added VIF rate limiting support for AWS Direct Connect, allowing customers to set bandwidth allocations on virtual interfaces to manage traffic on dedicated connections. (228a95dc)

Bug Fixes

• cloudfront-signer: filename asterisk apostrophe encoding fix (#8119) (35acab40)

---

For list of updated packages, view updated-packages.md in assets-3.1074.0.zip

Changelog

Sourced from @​aws-sdk/client-s3's changelog.

3.1075.0 (2026-06-23)

Note: Version bump only for package @​aws-sdk/client-s3

3.1074.0 (2026-06-22)

Note: Version bump only for package @​aws-sdk/client-s3

Commits

• 29ee199 Publish v3.1075.0
• c48dfa0 Publish v3.1074.0
• 74d0a07 chore(xml-builder): parse XML internally (#7863)
• See full diff in compare view

Updates @biomejs/biome from 2.5.0 to 2.5.1

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.1

2.5.1

Patch Changes

• #10722 f8a303d Thanks @​denbezrukov! - Fixed CSS formatter output for comments between import media queries.

  -@import url("print.css") print,
  -/* comment */
  -screen;
  +@import url("print.css") print, /* comment */ screen;

• #10738 9fdc560 Thanks @​JamBalaya56562! - Fixed #9899: the json and json-pretty reporters now escape backslashes in a diagnostic's location.path. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

  -    "path": "src\account\setup-passkey.tsx",
  +    "path": "src\\account\\setup-passkey.tsx",

• #10626 5f837df Thanks @​tom-groves! - Fixed #10625: biome migrate no longer emits an invalid trailing comma when a renamed rule (such as noConsoleLog → noConsole) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON biome.json with a parsing error.

• #10535 c245f9d Thanks @​Mokto! - Fixed a false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused.

• #10668 a0f197e Thanks @​Netail! - The biome init command has been updated to include a more up-to-date URL to the first-party extensions page.

• #10667 d8c3e87 Thanks @​Netail! - Fixed #10664: useErrorCause now correctly detects a shorthand property.

• #10696 ef2373f Thanks @​ematipico! - Fixed #9566. Improved how the Biome Language Server loads multiple configuration files inside a workspace.

• #10705 4ccb410 Thanks @​ematipico! - Fixed #10652. Biome plugins are now properly filtered when using --only and --skip flags.

• #10669 aa0a6eb Thanks @​Netail! - Fixed #10651: useInlineScriptId now correctly trims trivia to detect if an id attribute has been set.

• #10689 844b1be Thanks @​ematipico! - Fixed #10658. The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now disabled by default. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

  If you relied on this new feature, you must now turn on using the [editor settings] of the extension e.g. Zed and VSCode.

• #10695 043fbb5 Thanks @​ematipico! - Fixed #10674. Biome now throws an error when the field level is missing from a rule option.

• #10712 5941df2 Thanks @​Conaclos! - Improved the diagnostic and the documentation of useFlatMap.

• #10615 23814f1 Thanks @​qwertycxz! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

• #10688 ec69489 Thanks @​ematipico! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

• #10701 6c2e0d7 Thanks @​ematipico! - Fixed #10694. The Biome Language Server no longer prints an error when the user hovers a variable imported from node_modules.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.1

Patch Changes

• #10722 f8a303d Thanks @​denbezrukov! - Fixed CSS formatter output for comments between import media queries.

  -@import url("print.css") print,
  -/* comment */
  -screen;
  +@import url("print.css") print, /* comment */ screen;

• #10738 9fdc560 Thanks @​JamBalaya56562! - Fixed #9899: the json and json-pretty reporters now escape backslashes in a diagnostic's location.path. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

  -    "path": "src\account\setup-passkey.tsx",
  +    "path": "src\\account\\setup-passkey.tsx",

• #10626 5f837df Thanks @​tom-groves! - Fixed #10625: biome migrate no longer emits an invalid trailing comma when a renamed rule (such as noConsoleLog → noConsole) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON biome.json with a parsing error.

• #10535 c245f9d Thanks @​Mokto! - Fixed a false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused.

• #10668 a0f197e Thanks @​Netail! - The biome init command has been updated to include a more up-to-date URL to the first-party extensions page.

• #10667 d8c3e87 Thanks @​Netail! - Fixed #10664: useErrorCause now correctly detects a shorthand property.

• #10696 ef2373f Thanks @​ematipico! - Fixed #9566. Improved how the Biome Language Server loads multiple configuration files inside a workspace.

• #10705 4ccb410 Thanks @​ematipico! - Fixed #10652. Biome plugins are now properly filtered when using --only and --skip flags.

• #10669 aa0a6eb Thanks @​Netail! - Fixed #10651: useInlineScriptId now correctly trims trivia to detect if an id attribute has been set.

• #10689 844b1be Thanks @​ematipico! - Fixed #10658. The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now disabled by default. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

  If you relied on this new feature, you must now turn on using the [editor settings] of the extension e.g. Zed and VSCode.

• #10695 043fbb5 Thanks @​ematipico! - Fixed #10674. Biome now throws an error when the field level is missing from a rule option.

• #10712 5941df2 Thanks @​Conaclos! - Improved the diagnostic and the documentation of useFlatMap.

• #10615 23814f1 Thanks @​qwertycxz! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

• #10688 ec69489 Thanks @​ematipico! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

• #10701 6c2e0d7 Thanks @​ematipico! - Fixed #10694. The Biome Language Server no longer prints an error when the user hovers a variable imported from node_modules.

• #10681 888515b Thanks @​Conaclos! - Fixed useExportType that reported useless details in some diagnostics.

... (truncated)

Commits

• ffe7d33 chore: revert
• 564d660 chore: revert
• 0abf1a5 ci: release (#10627)
• 23814f1 chore(biome_configuration): add allowTrailingCommas to json-schema to make VS...
• a0f197e chore: dead and old links (#10668)
• See full diff in compare view

Updates fallow from 2.101.0 to 2.102.0

Release notes

Sourced from fallow's releases.

v2.102.0: code review brief, decision surface, and symbol-level trace

Code review for changed code

This release adds a toolkit for reviewing changed code, designed for both human reviewers and AI agents.

Review brief (fallow review, or fallow audit --brief)

A new advisory orientation mode over changed code. It runs the same dead-code + complexity + duplication analysis as fallow audit but answers "where do I look?" instead of "will CI block this?": it ALWAYS exits 0 (the verdict is carried informationally), so a reviewer or agent can read it regardless of the gate outcome. The brief renders a ranked decision surface, a weighted focus map, and change-impact context. --format is orthogonal to --brief.

Decision surface (fallow decision-surface and the decision_surface MCP tool)

Surfaces the consequential structural decisions a change embeds: a ranked, capped (3 to 5) set of coupling/boundary, public-API/contract, and dependency decisions, each framed as a judgment question with the routed expert to ask. Each decision carries an honest count of how many internal consumers it affects plus an explicit trade-off clause, so the reader sees the cost as well as the call. It is separable and cheap, advisory (always exits 0), and every decision is suppressible with // fallow-ignore. Use --base / --changed-since to pick the comparison point, exactly like fallow audit.

Symbol-level call chains (fallow trace <FILE:SYMBOL>)

Walks callers up (modules that import the symbol) and callees down (import-symbol edges plus intra-module call sites) through the module graph, bounded by --depth (default 2). Use --callers / --callees to scope the direction; both are walked by default. Best-effort and syntactic per ADR-001: resolved-vs-unresolved callees are reported honestly, never silently dropped.

fallow trace src/utils.ts:formatDate

Agent-contract walkthrough loop

For agents that review changed code, fallow audit --walkthrough-guide emits a deterministic digest (the brief, the decision surface, the review direction, the JSON schema the agent must return, and a graph-snapshot hash) built from the graph only, so PR prose is never folded in and the digest is injection-resistant. The agent produces judgment JSON and reopens with --walkthrough-file, which post-validates it against the LIVE graph: it rejects any judgment whose signal_id fallow did not emit (anti-hallucination) and refuses the whole payload as stale when the snapshot hash no longer matches. The verifier is the graph, not a second model. Both flags always exit 0.

A weighted focus map ranks changed units by review weight and collapses the de-prioritized tail by default; --show-deprioritized re-expands it (the deprioritized list is always present in --format json).

Framework health

• Astro framework-health detection. .astro components now participate in the same health suite as Vue/Svelte/Angular/React: a reachable component rendered in no template surfaces as unrendered-component, an interface Props field read nowhere surfaces as unused-component-prop, and fallow health now scores .astro complexity. A zero-false-positive abstain ladder protects public surfaces. No new rules or severities.
• Lit / web-component framework-health detection. A custom element registered via @customElement / customElements.define but rendered as a tag in no html template surfaces as unrendered-component, and a @state() reactive property read nowhere surfaces as unused-class-member. @property (the public attribute API) is never flagged. Gated on a lit / lit-element / @lit/reactive-element dependency.
• Deeper React prop coverage for unused-component-prop. The React arm now harvests props from same-file typed interfaces and generic forwardRef components, not only inline destructure, while still abstaining on imported prop interfaces and exported public-API components.

Editor

• React component intelligence. The LSP surfaces ambient React/Preact context with no new rule, finding, or severity. A code lens above each component summarizes render count, props, and hooks; a per-prop hover shows where a prop is read and passed from; a forwarded prop shows its forwarding chain. Editor-only context: fallow / audit / --format json output is unchanged.
• VS Code: clearer tree badges, hardened health spawn, and de-duplicated diagnostics.

Security

• LLM-call prompt-injection candidate. A new llm-call-injection category (CWE-1427) in the fallow security tainted-sink catalogue. It fires only when an untrusted source flows into the prompt/messages argument of a known LLM-call sink (a taint path into the call, not every LLM call). Like all fallow security output it is a candidate for verification, not a verified vulnerability, and never appears under bare fallow or the audit gate.

Fixed

• Merged namespace values imported through star barrels are no longer falsely reported as unused. A value export sharing its name with an export declare namespace and consumed through export * now receives the same named-import credit as a direct import. Thanks @​TeoVezza95 for the report. (#1373)
• VS Code now resolves the native fallow binary from platform packages when the binary is reached through a .cmd / .ps1 launcher shim on PATH, so LSP-backed diagnostics start reliably. Thanks @​ivan-palatov for the report. (#1359)
• TanStack Router: custom routeFileIgnorePrefix is honored, so files using a configured ignore prefix are no longer flagged as dead code. Thanks @​Spiralis for the report. (#1358)
• fallow audit base-snapshot worktree paths are unique per call, so concurrent audit runs no longer collide.
• More precise telemetry failure classification when telemetry is enabled.
• Vendored GitLab CI now bundles gitlab_common.sh, so fallow ci-template gitlab --vendor pipelines run without reaching out to raw.githubusercontent.com.

... (truncated)

Changelog

Sourced from fallow's changelog.

[2.102.0] - 2026-06-23

Added

• Code review brief (fallow review, or fallow audit --brief). A new advisory orientation mode over changed code. It runs the same dead-code + complexity + duplication analysis as fallow audit but answers "where do I look?" instead of "will CI block this?": it ALWAYS exits 0 (the verdict is carried informationally), so a reviewer or agent can read it regardless of the gate outcome. The brief renders a ranked decision surface, a weighted focus map, and change-impact context. --format is orthogonal to --brief. fallow review is an alias for fallow audit --brief.

• fallow decision-surface command and decision_surface MCP tool. Surfaces the consequential structural decisions a change embeds (the apex of the review brief): a ranked, capped (3-5) set of coupling/boundary, public-API/contract, and dependency decisions, each framed as a judgment question with the routed expert to ask. Each decision carries an honest count of how many internal consumers it affects plus an explicit trade-off clause, so the reader sees the cost as well as the call. Separable and cheap, advisory (always exits 0), and every decision is suppressible with // fallow-ignore. Use --base / --changed-since to pick the comparison point, exactly like fallow audit.

• fallow trace <FILE:SYMBOL> symbol-level call chains. Walks callers UP (modules that import the symbol) and callees DOWN (import-symbol edges plus intra-module call sites) through the module graph, bounded by --depth (default 2). --callers / --callees scope the direction; both are walked by default. Best-effort and syntactic per ADR-001: resolved-vs-unresolved callees are reported honestly, never silently dropped. It is its own surface, never folded into the ranked review brief.

• Agent-contract walkthrough loop (--walkthrough-guide / --walkthrough-file). --walkthrough-guide emits a deterministic digest (the brief, the decision surface, the review direction, the JSON schema the agent must return, and a graph-snapshot hash) built from the graph only, so PR prose is never folded in and the digest is injection-resistant. --walkthrough-file ingests an agent's judgment JSON and post-validates it against the LIVE graph: it rejects any judgment whose signal_id fallow did not emit (anti-hallucination) and refuses the whole payload as stale when the echoed graph-snapshot hash no longer matches. The verifier is the graph, not a second model. Both imply the brief and always exit 0.

• Weighted focus map with a de-prioritized escape hatch. The review brief ranks changed units by review weight and collapses the de-prioritized tail by default; --show-deprioritized re-expands the human render. The deprioritized list is always present in --format json regardless of the flag.

• LLM-call prompt-injection candidate (fallow security). A new llm-call-injection category (CWE-1427) in the tainted-sink catalogue. It fires only when an untrusted source flows into the prompt/messages argument of a known LLM-call sink (a taint PATH into the call, not every LLM call), pinned to the distinctive LLM SDK call shapes. Like all fallow security output it is a CANDIDATE for verification, not a verified vulnerability, and never appears under bare fallow or the audit gate.

... (truncated)

Commits

• 8a83dc0 chore: release v2.102.0
• b5e53b5 fix(dead-code): credit merged namespace star re-export values
• e890fbe chore(deps): bump napi from 3.9.0 to 3.9.2 (#1381)
• 2238983 chore(deps): bump insta from 1.47.2 to 1.48.0 (#1380)
• 4059812 chore(deps-dev): bump oxfmt from 0.54.0 to 0.55.0 (#1378)
• 01e2813 chore(deps): bump rust-lang/crates-io-auth-action from 1.0.4 to 1.0.5 (#1375)
• eb55b34 chore(deps-dev): bump @​tanstack/intent in /npm/fallow (#1376)
• 7b8c570 chore(deps-dev): bump oxlint from 1.69.0 to 1.70.0 (#1377)
• e585f05 refactor(review-app): namespace persisted state under fallow-review instead o...
• 0ffd4ca test(unused-members): cover issue-844 typed-instance crediting at monorepo pa...
• Additional commits viewable in compare view

Updates @posthog/react from 1.10.2 to 1.10.3

Release notes

Sourced from @​posthog/react's releases.

@​posthog/react@​1.10.3

1.10.3

Patch Changes

• #3905 870cfa4 Thanks @​marandaneto! - Filter disabled bootstrap feature flags from useActiveFeatureFlags. (2026-06-22)
• Updated dependencies [1fce04f]:
  • posthog-js@1.391.8

Changelog

Sourced from @​posthog/react's changelog.

1.10.3

Patch Changes

• #3905 870cfa4 Thanks @​marandaneto! - Filter disabled bootstrap feature flags from useActiveFeatureFlags. (2026-06-22)
• Updated dependencies [1fce04f]:
  • posthog-js@1.391.8

Commits

• bafe192 chore: update versions and lockfile [version bump]
• 870cfa4 fix(react): filter disabled bootstrap active flags (#3905)
• See full diff in compare view

Updates @ricky0123/vad-web from 0.0.17 to 0.0.30

Commits

• See full diff in compare view

Updates @sentry/react from 10.59.0 to 10.61.0

Release notes

Sourced from @​sentry/react's releases.

10.61.0

Important Changes

• feat(core): Enable streamGenAiSpans by default (#21732)

  The SDK now extracts all gen_ai spans out of a transaction and sends them as v2 envelope items by default. This prevents gen_ai spans from being dropped when the transaction payload exceeds size limits. Because they are no longer constrained by transaction size limits, AI message data is also no longer truncated by default. Set enableTruncation: true on the respective AI integration to re-enable truncation. To keep the previous behavior, set streamGenAiSpans: false.

  Self-hosted Sentry users should opt out with streamGenAiSpans: false, since streamed gen_ai spans may not be ingested by their Sentry instance.

Other Changes

• feat(cloudflare): Add batch, exec, and withSession D1 instrumentation (#21292)
• feat(cloudflare): Instrument SQL API in sqlite durable objects (#21656)
• feat(core): Add db.query.summary functionality (#21670)
• feat(core): Add top-level Sentry.setAttribute(s) APIs (#21705)
• fix(hono): Name transactions after the matched route handler (#21700)
• fix(react-router): Bump peerDependencies for react-router 8 (#21762)
• fix(replays): Record replay trace_ids with span streaming (#21714)

• build: add rollup plugin for compile-time ESM/CJS code branching (#21715)
• chore: Fix version bump for bundler plugin fixtures (#21707)
• chore(node-integration-tests): Improve node test runner naming (#21685)
• docs: Update contributing guide for E2E tests (#21763)
• feat: Adopt bindTracingChannelToSpan across runtimes (#21642)
• feat: Remove Otel from fsIntegration (#21654)
• feat(deps): Bump http-proxy-middleware from 2.0.9 to 2.0.10 (#21709)
• feat(server-utils): Add tracingChannel-to-span binding (#21641)
• fix(tests): Add dedicated route for Hono query_string tests (#21731)
• ref: Export SPAN_KIND from core and drop OTel SpanKind imports (#21668)
• test: Make bundler plugins tests work after release
• test: Remove duplicated test (#21699)
• test: retry npm install on network hiccups (#21689)
• test(cloudflare): Increase node count for memory tests (#21719)
• test(e2e): Add sentry-sdk-init measure and marks (#21687)
• test(e2e): Add more lighthouse react e2e test SDK init modes (#21711)
• test(node): Add esm/cjs specific test runner utils (#21729)
• test(node): Increase cron integration test timeout to 60s (#21704)
• test(node): Streamline amqplib tests (#21723)
• test(node): Update mysql tests for better coverage and correctness (#21684)
• test(node): Use different ports for redis tests (#21727)

Bundle size 📦

Path	Size

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

10.61.0

Important Changes

• feat(core): Enable streamGenAiSpans by default (#21732)

  The SDK now extracts all gen_ai spans out of a transaction and sends them as v2 envelope items by default. This prevents gen_ai spans from being dropped when the transaction payload exceeds size limits. Because they are no longer constrained by transaction size limits, AI message data is also no longer truncated by default. Set enableTruncation: true on the respective AI integration to re-enable truncation. To keep the previous behavior, set streamGenAiSpans: false.

  Self-hosted Sentry users should opt out with streamGenAiSpans: false, since streamed gen_ai spans may not be ingested by their Sentry instance.

Other Changes

• feat(cloudflare): Add batch, exec, and withSession D1 instrumentation (#21292)
• feat(cloudflare): Instrument SQL API in sqlite durable objects (#21656)
• feat(core): Add db.query.summary functionality (#21670)
• feat(core): Add top-level Sentry.setAttribute(s) APIs (#21705)
• fix(hono): Name transactions after the matched route handler (#21700)
• fix(react-router): Bump peerDependencies for react-router 8 (#21762)
• fix(replays): Record replay trace_ids with span streaming (#21714)

• build: add rollup plugin for compile-time ESM/CJS code branching (#21715)
• chore: Fix version bump for bundler plugin fixtures (#21707)
• chore(node-integration-tests): Improve node test runner naming (#21685)
• docs: Update contributing guide for E2E tests (#21763)
• feat: Adopt bindTracingChannelToSpan across runtimes (#21642)
• feat: Remove Otel from fsIntegration (#21654)
• feat(deps): Bump http-proxy-middleware from 2.0.9 to 2.0.10 (#21709)
• feat(server-utils): Add tracingChannel-to-span binding (#21641)
• fix(tests): Add dedicated route for Hono query_string tests (#21731)
• ref: Export SPAN_KIND from core and drop OTel SpanKind imports (#21668)
• test: Make bundler plugins tests work after release
• test: Remove duplicated test (#21699)
• test: retry npm install on network hiccups (#21689)
• test(cloudflare): Increase node count for memory tests (#21719)
• test(e2e): Add sentry-sdk-init measure and marks (#21687)
• test(e2e): Add more lighthouse react e2e test SDK init modes (#21711)
• test(node): Add esm/cjs specific test runner utils (#21729)
• test(node): Increase cron integration test timeout to 60s (#21704)
• test(node): Streamline amqplib tests (#21723)
• test(node): Update mysql tests for better coverage and correctness (#21684)
• test(node): Use different ports for redis tests (#21727)

10.60.0

Other Changes

... (truncated)

Commits

• a5f654b release: 10.61.0
• c3f2b30 Merge pull request #21774 from getsentry/prepare-release/10.61.0
• fcf3dc9 meta(changelog): Update changelog for 10.61.0
• 28cffd1 docs: Update contributing guide for E2E tests (#21763)
• b72a360 feat(cloudflare): Instrument SQL API in sqlite durable objects (#21656)
• a8de444 fix(react-router): Bump peerDependencies for react-router 8 (#21762)
• 2905c3a feat(cloudflare): Add batch, exec, and withSession D1 instrumentation (#21292)
• b31ef48 fix(tests): Add dedicated route for Hono query_string tests (#21731)
• ce6f731 test(node): Update mysql tests for better coverage and correctness (#21684)
• ff4c9ba chore(github): Add cron schedule for "track framework updates" (#21754)
• Additional commits viewable in compare view

Updates @tanstack/query-async-storage-persister from 5.101.0 to 5.101.1

Release notes

Sourced from @​tanstack/query-async-storage-persister's releases.

@​tanstack/query-async-storage-persister@​5.101.1

Patch Changes

• Updated dependencies [9eff92e]:
  • @​tanstack/query-core@​5.101.1
  • @​tanstack/query-persist-client-core@​5.101.1

Changelog

Sourced from @​tanstack/query-async-storage-persister's changelog.

5.101.1

Patch Changes

• Updated dependencies [9eff92e]:
  • @​tanstack/query-core@​5.101.1
  • @​tanstack/query-persist-client-core@​5.101.1

Commits

• b809297 ci: Version Packages (#10977)
• ee89b90 test(query-async-storage-persister): replace deprecated 'toBeCalledTimes' wit...
• See full diff in compare view

Updates @tanstack/react-query from 5.101.0 to 5.101.1

Release notes

Sourced from @​tanstack/react-query's releases.

@​tanstack/react-query-devtools@​5.101.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-devtools@​5.101.1
  • @​tanstack/react-query@​5.101.1

@​tanstack/react-query-next-experimental@​5.101.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/react-query@​5.101.1

@​tanstack/react-query-persist-client@​5.101.1

Patch Changes

• Updated dependencies []:
  • @​tanstack/query-persist-client-core@​5.101.1
  • @​tanstack/react-query@​5.101.1

@​tanstack/react-query@​5.101.1

Patch Changes

• Updated dependencies [9eff92e]:
  • @​tanstack/query-core@​5.101.1

Changelog

Sourced from @​tanstack/react-query's changelog.

5.101.1

Patch Changes

• Updated dependencies [9eff92e]:
  • @​tanstack/query-core@​5.101.1

Commits

• b809297 ci: Version Packages (#10977)
• ccc843e test({react,preact}-query/useQueries): move type-only tests to 'useQueries.te...
• 4154613...

  Description has been truncated

[greptile-apps]

PR author is not in the allowed authors list.

[github-actions]

✅ Tests passed — 1414/1418

Suite	Passed	Failed	Skipped
✅ agent	279/279	0	0
✅ build	24/24	0	0
⚠️ claw-app	0/0	0	0
⚠️ claw-onboard	0/0	0	0
⚠️ claw-server	0/0	0	0
✅ eval	91/91	0	0
✅ server-agent	301/301	0	0
✅ server-api	143/143	0	0
✅ server-browser	10/10	0	0
✅ server-integration	10/10	0	0
✅ server-lib	257/258	0	1
✅ server-root	47/50	0	3
✅ server-tools	252/252	0	0

View workflow run

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.