chore(deps): bump the frontend-dependencies group across 1 directory with 20 updates

[dependabot]

Bumps the frontend-dependencies group with 20 updates in the /frontend directory:

Package	From	To
@capacitor/android	8.5.0	8.5.1
@capacitor/camera	8.2.2	8.2.4
@capacitor/core	8.5.0	8.5.1
@capacitor/geolocation	8.2.1	8.2.2
@capacitor/ios	8.5.0	8.5.1
@sentry/react	10.70.0	10.74.0
i18next	26.3.6	26.4.2
onnxruntime-web	1.27.0	1.29.0
react	19.2.8	19.3.0
react-dom	19.2.8	19.3.0
react-i18next	17.0.11	17.0.13
@axe-core/playwright	4.12.1	4.13.0
@capacitor/cli	8.5.0	8.5.1
@playwright/test	1.62.1	1.63.0
@testing-library/react	16.3.2	16.3.3
@testing-library/user-event	14.6.3	14.6.7
@vitejs/plugin-react	6.0.5	6.1.1
sharp	0.35.3	0.35.4
vite	8.2.1	8.3.0
vitest	4.1.10	5.0.0

Updates @capacitor/android from 8.5.0 to 8.5.1

Release notes

Sourced from @​capacitor/android's releases.

8.5.1

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Changelog

Sourced from @​capacitor/android's changelog.

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Commits

• 0c9e35d Release 8.5.1
• ee586ae fix: block navigation to the internal HTTP proxy path
• 5ac4dd6 fix(core): prevent removeListener from removing wrong listener (#8271)
• 5e5bb3b fix(cli): use POSIX paths in CapApp-SPM Package.swift (#8549)
• See full diff in compare view

Updates @capacitor/camera from 8.2.2 to 8.2.4

Release notes

Sourced from @​capacitor/camera's releases.

v8.2.4

8.2.4 (2026-09-01)

Bug Fixes

• ios: align ion-ios-camera version range across SwiftPM and CocoaPods (#79) (89e7b58), closes #46 #50 #66 #77
• ios: bump ion-ios-camera to 2.0.0 (#77) (9e227e8)

---

This release is also available on:

• npm package (@​latest dist-tag)

v8.2.3

8.2.3 (2026-08-19)

Bug Fixes

• android: only apply kotlin-android plugin if not already applied (#71) (32f3094)

---

This release is also available on:

• npm package (@​latest dist-tag)

v8.2.3-next.1

8.2.3-next.1 (2026-08-03)

Bug Fixes

• ios: bump ion-ios-camera to 1.0.5 for iOS 27 UIScene compliance (#67) (b110010)

---

This release is also available on:

• npm package (@​next dist-tag)

Changelog

Sourced from @​capacitor/camera's changelog.

8.2.4 (2026-09-01)

Bug Fixes

• ios: align ion-ios-camera version range across SwiftPM and CocoaPods (#79) (89e7b58), closes #46 #50 #66 #77
• ios: bump ion-ios-camera to 2.0.0 (#77) (9e227e8)

8.2.3 (2026-08-19)

Bug Fixes

• android: only apply kotlin-android plugin if not already applied (#71) (32f3094)

Commits

• e1a47e6 chore(release): 8.2.4 [skip ci]
• 89e7b58 fix(ios): align ion-ios-camera version range across SwiftPM and CocoaPods (#79)
• 9e227e8 fix(ios): bump ion-ios-camera to 2.0.0 (#77)
• bf45acb chore(release): 8.2.3 [skip ci]
• 32f3094 fix(android): only apply kotlin-android plugin if not already applied (#71)
• See full diff in compare view

Updates @capacitor/core from 8.5.0 to 8.5.1

Release notes

Sourced from @​capacitor/core's releases.

8.5.1

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Changelog

Sourced from @​capacitor/core's changelog.

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Commits

• 0c9e35d Release 8.5.1
• ee586ae fix: block navigation to the internal HTTP proxy path
• 5ac4dd6 fix(core): prevent removeListener from removing wrong listener (#8271)
• 5e5bb3b fix(cli): use POSIX paths in CapApp-SPM Package.swift (#8549)
• See full diff in compare view

Updates @capacitor/geolocation from 8.2.1 to 8.2.2

Release notes

Sourced from @​capacitor/geolocation's releases.

v8.2.2

8.2.2 (2026-08-13)

Bug Fixes

• android: only apply kotlin-android plugin if not already applied (#97) (d7024ed)

---

This release is also available on:

• npm package (@​latest dist-tag)

Changelog

Sourced from @​capacitor/geolocation's changelog.

8.2.2 (2026-08-13)

Bug Fixes

• android: only apply kotlin-android plugin if not already applied (#97) (d7024ed)

Commits

• 5df28c2 chore(release): 8.2.2 [skip ci]
• b94274d docs: fix unclosed admonitions (#99)
• d7024ed fix(android): only apply kotlin-android plugin if not already applied (#97)
• See full diff in compare view

Updates @capacitor/ios from 8.5.0 to 8.5.1

Release notes

Sourced from @​capacitor/ios's releases.

8.5.1

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Changelog

Sourced from @​capacitor/ios's changelog.

8.5.1 (2026-08-31)

Bug Fixes

• block navigation to the internal HTTP proxy path (ee586ae)
• cli: use POSIX paths in CapApp-SPM Package.swift (#8549) (5e5bb3b)
• core: prevent removeListener from removing wrong listener (#8271) (5ac4dd6)

Commits

• 0c9e35d Release 8.5.1
• ee586ae fix: block navigation to the internal HTTP proxy path
• 5ac4dd6 fix(core): prevent removeListener from removing wrong listener (#8271)
• 5e5bb3b fix(cli): use POSIX paths in CapApp-SPM Package.swift (#8549)
• See full diff in compare view

Updates @sentry/react from 10.70.0 to 10.74.0

Release notes

Sourced from @​sentry/react's releases.

10.74.0

• feat(v10): Streamline isolation scope handling & reset in isolation scopes (#24152)
• fix(server-utils): Include Gemini reasoning tokens in Vercel AI token usage (#23433)
• fix(v10/browser): Set user_agent.original on all spans for consistent filtering (#24226)
• fix(v10/cloudflare): Auto-instrument classes re-exported from the worker entry (#24181)
• fix(v10/core): Guard loadModule default parameter against ESM scope (#24154)
• fix(v10/core): Match wrapped Facebook Mobile browser errors in DEFAULT_IGNORE_ERRORS (#23877)
• fix(v10/core): Resolve MCP capture policy per operation (#23796)
• fix(v10/nextjs): Fix SDK import crashing under jsdom/happy-dom (#23906)
• fix(v10/nextjs): Keep the Pages Router runtime out of App Router client bundles (#24223)
• fix(v10/nextjs): Register Vercel AI span processors on Next.js (#23773)
• fix(v10/nuxt): Windows file:// for import-in-the-middle hook and isAbsolute for C:\ (#24026)
• fix(v10/profiling-node): Bump @​sentry/node-cpu-profiler to 2.4.4 (#24238)
• fix(v10/sveltekit): Handle SvelteKit 3 error kinds in handleErrorWithSentry (#23995)
• fix(v10/sveltekit): Read Cloudflare execution context from platform.ctx (#23994)
• fix(v10/sveltekit): Read SvelteKit config from the Vite plugin (#23998)

• test(e2e): Assert Next.js Cloudflare worker bundle stays free of orchestrion bundler plugins (#23910)

Work in this release was contributed by @​halillusion and @​zkasuran. Thank you for your contributions!

Bundle size 📦

Path	Size
@​sentry/browser	27.12 KB
@​sentry/browser - with treeshaking flags	25.59 KB
@​sentry/browser (incl. Tracing)	45.53 KB
@​sentry/browser (incl. Tracing + Span Streaming)	47.29 KB
@​sentry/browser (incl. Tracing, Profiling)	50.18 KB
@​sentry/browser (incl. Tracing, Replay)	83.87 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	73.74 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	88.49 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	100.82 KB
@​sentry/browser (incl. Feedback)	43.89 KB
@​sentry/browser (incl. sendFeedback)	31.8 KB
@​sentry/browser (incl. FeedbackAsync)	36.82 KB
@​sentry/browser (incl. Metrics)	28.19 KB
@​sentry/browser (incl. Logs)	28.41 KB
@​sentry/browser (incl. Metrics & Logs)	29.09 KB
@​sentry/react	28.89 KB
@​sentry/react (incl. Tracing)	47.74 KB
@​sentry/vue	32.42 KB
@​sentry/vue (incl. Tracing)	47.47 KB
@​sentry/svelte	27.15 KB

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

10.74.0

• feat(v10): Streamline isolation scope handling & reset in isolation scopes (#24152)
• fix(server-utils): Include Gemini reasoning tokens in Vercel AI token usage (#23433)
• fix(v10/browser): Set user_agent.original on all spans for consistent filtering (#24226)
• fix(v10/cloudflare): Auto-instrument classes re-exported from the worker entry (#24181)
• fix(v10/core): Guard loadModule default parameter against ESM scope (#24154)
• fix(v10/core): Match wrapped Facebook Mobile browser errors in DEFAULT_IGNORE_ERRORS (#23877)
• fix(v10/core): Resolve MCP capture policy per operation (#23796)
• fix(v10/nextjs): Fix SDK import crashing under jsdom/happy-dom (#23906)
• fix(v10/nextjs): Keep the Pages Router runtime out of App Router client bundles (#24223)
• fix(v10/nextjs): Register Vercel AI span processors on Next.js (#23773)
• fix(v10/nuxt): Windows file:// for import-in-the-middle hook and isAbsolute for C:\ (#24026)
• fix(v10/profiling-node): Bump @​sentry/node-cpu-profiler to 2.4.4 (#24238)
• fix(v10/sveltekit): Handle SvelteKit 3 error kinds in handleErrorWithSentry (#23995)
• fix(v10/sveltekit): Read Cloudflare execution context from platform.ctx (#23994)
• fix(v10/sveltekit): Read SvelteKit config from the Vite plugin (#23998)

• test(e2e): Assert Next.js Cloudflare worker bundle stays free of orchestrion bundler plugins (#23910)

Work in this release was contributed by @​halillusion and @​zkasuran. Thank you for your contributions!

10.73.0

Important Changes

• feat(v10/nextjs): Add @sentry/nextjs/config entry point (#23766)

  withSentryConfig is now available from @sentry/nextjs/config, the path it moves to in v11. Importing it from @sentry/nextjs still works on v10 but logs a warning once, so you can change your next.config file today and upgrade to v11 without touching it again.

  // next.config.mjs
  - import { withSentryConfig } from '@sentry/nextjs';
  + import { withSentryConfig } from '@sentry/nextjs/config';

Other Changes

• feat(v10/node): Deprecate shouldHandleError on setupExpressErrorHandler and setupFasitfyErrorHandler (#23734)
• fix(v10/cloudflare): Instrument Durable Object handlers installed as read-only properties (#23769)

• test(v10/nextjs): Drop nextjs-16-cf-workers canary variant (#23775)

... (truncated)

Commits

• ce5009a release: 10.74.0
• 4b24ddd meta(changelog): Update changelog for 10.74.0 (#24252)
• 371ed5d fix(v10/profiling-node): Bump @​sentry/node-cpu-profiler to 2.4.4 (#24238)
• 9f38e48 fix(v10/browser): Set user_agent.original on all spans for consistent filte...
• 264f990 fix(v10/cloudflare): Auto-instrument classes re-exported from the worker entr...
• c89f6e6 fix(v10/nextjs): Keep the Pages Router runtime out of App Router client bundl...
• de25dcb fix(v10/core): Guard loadModule default parameter against ESM scope (#24154)
• b627037 feat(v10): Streamline isolation scope handling & reset in isolation scopes (#...
• 2ce0ea1 fix(v10/nuxt): Windows file:// for import-in-the-middle hook and isAbsolute f...
• 3e0eccc fix(server-utils): Include Gemini reasoning tokens in Vercel AI token usage (...
• Additional commits viewable in compare view

Updates i18next from 26.3.6 to 26.4.2

Release notes

Sourced from i18next's releases.

v26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

v26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

v26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

Changelog

Sourced from i18next's changelog.

26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

Commits

• 4dba50f 26.4.2
• e436b62 build
• d955fb0 fix: stringify formatter results in nested values, changelog v26.4.2
• dfafa3c fix: keep replacement patterns literal in nested values (#2447)
• 3c9981e chore: keep dev-only and local files out of the npm package
• c057ee0 26.4.1
• 02e3e16 changelog v26.4.1
• 6f198f2 fix(types): allow selector keyPrefix in getFixedT under enableSelector 'stric...
• 652847e 26.4.0
• 6c6025f prettier fix
• Additional commits viewable in compare view

Updates onnxruntime-web from 1.27.0 to 1.29.0

Release notes

Sourced from onnxruntime-web's releases.

ONNX Runtime v1.29.0

Announcements & Breaking Changes

• onnxruntime-web has announced the deprecation of WebGL and JSEP. The native WebGPU EP is the recommended path going forward. See the deprecation and migration plans for details (#29716, #31683).
• POSIX telemetry is now available on Linux, macOS, Android, and iOS when ONNX Runtime is built with telemetry enabled. It does not change the public ABI, WebAssembly remains telemetry-free, and setting ORT_DISABLE_TELEMETRY=1 before initialization disables non-Windows telemetry for the process (#27379, #29872).
• The unused internal onnxruntime/python/tools/tensorrt dashboard tooling was removed. This does not affect the TensorRT Execution Provider APIs (#29395).

Security Fixes

Path, bounds, and input validation

• Fixed a path traversal vulnerability in TensorRT and NvTensorRTRTX engine refitting by making external-data path validation unconditional (#29396).
• Validated the CPU MoE k attribute against the number of experts and fixed a CPU TensorScatter security issue (#29907, #29916).
• Added missing rank, shape, and parameter validation for pooling, LSTM and DynamicQuantizeLSTM, Sampling, FeatureVectorizer, SkipLayerNorm, QLinearConv, Whisper decoding, RNN activations, GridSample, contrib Range, and CropAndResize (#29254, #29255, #29265, #29579, #29595, #29605, #29871, #31636, #31671, #31675, #31676, #31684).
• Hardened CUDA indexing and buffer handling in GridSample, transpose, GatherBlockQuantized, InstanceNormalization, LayerNorm/RMSNorm, BeamSearch, DeformConv, AveragePool, and MaxPool (#29581, #29631, #29638, #31640, #31642, #31644, #31645, #31647, #31650).
• Fixed packed sub-byte tensor over-copying in OrtApi::GetValue and validated DML constant tensor byte sizes (#29157, #31665).

Supply chain and tooling

• Updated npm lockfiles, refreshed the Next.js end-to-end fixture lockfile for security advisories, and upgraded adm-zip for onnxruntime-node (#29827, #29926, #31192).

New Features

Core APIs & Runtime

• Default intra-op and inter-op thread-pool sizes can now be set with ORT_INTRA_OP_NUM_THREADS and ORT_INTER_OP_NUM_THREADS. Explicit thread settings still take precedence, and 0 preserves machine-sized defaults (#29688).
• Added weightless-model support for all initializer types, allowed zero-input EpContext nodes, and wired maximum-shape inference into workspace estimation (#29607, #29799, #31613).
• Added ONNX-domain support for rotary embedding and a fused MRotaryEmbedding contrib operator for Qwen mRoPE variants (#29261, #31728).
• Added multi-shape profiling to onnxruntime_perf_test through --data_shape, plus verbose graph-transformer tracing and broader inference-session error-path coverage (#29555, #29558, #29569, #29571).

Execution Provider ABI & Plugin EPs

• WebGPU now supports device-free compile-only sessions for offline graph transformation (#29681).
• Expanded CUDA plugin EP packaging and testing, including Windows ARM64 package and size options, updated package outputs, and aligned architecture selections across Python, C API, TensorRT, Node.js, and plugin packages (#31635, #31722, #31992).
• Improved plugin lifecycle handling by unloading failed EP library loads and fixing allocator-deleter lifetime (#29634, #29770).

Execution Provider Updates

NVIDIA CUDA EP

Attention and decoding

• Added PagedAttention with quantized KV cache, XQA decode, MLA, QK-Norm, and head-sink support (#29912).
• Extended quantized KV-cache support with attention sinks, independent and per-channel scales, sliding-window cache support, and a fused K/V dequantization launch (#29900, #29904, #31480).
• Added a cuDNN SDPA decode tier to the standard ONNX Attention CUDA kernel and enabled cuDNN SDPA for contrib Attention (#29715, #29717).
• Added attention_bias support to the GroupQueryAttention unfused path and state_window support to LinearAttention and CausalConvWithState for MTP (#29525, #31157).
• Fixed LinearAttention on GPUs with limited shared memory (#31982).

MoE and quantized GEMM

... (truncated)

Commits

• 2e2543f [CUDA] Update cuda archs in packaging pipelines (#31992)
• 9b174a4 [CUDA] Add GatedAdd contrib operator (#31835)
• a29da16 Validate SkipLayerNorm prepacked lengths (#31676)
• 831fa2f Validate whisper beginning_timestamp_token_id bounds (#31636)
• 3cee186 Handle RNN activation parameters safely (#31675)
• 37d79e3 Harden CUDA fp16 transpose index math against int overflow (#31644)
• 45bdd4c Validate QLinearConv bias size against output channels (#31684)
• f5de4c3 Fix TfIdfVectorizer weight indexing semantics (#31649)
• d3abafc Validate FeatureVectorizer batch sizes (#31671)
• 1441b36 [WebGPU] Add MRotaryEmbedding support (#31976)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for onnxruntime-web since your current version.

Updates react from 19.2.8 to 19.3.0

Release notes

Sourced from react's releases.

19.3.0 (September 9, 2026)

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.3 release post for more information.

New React Features

• <ViewTransition />: Adds <ViewTransition /> and addTransitionType APIs to power View Transition animations in React (@​sebmarkbage, @​jackpope, @​gaearon: #31975, #31987, #31996, #31999, #32001, #32002, #32028, #32029, #32031, #32034, #32038, #32041, #32050, #32090, #32105, #32254, #32379, #32422, #32462, #32540, #32545, #32585, #32599, #32611, #32612, #32617, #32651, #32653, #32656, #32664, #32699, #32723, #32734, #32751, #32752, #32760, #32761, #32764, #32772, #32790, #32819, #32820, #32822, #32833, #32849, #33094, #33191, #33200, #33206, #33293, #33330, #33331, #33332, #33357, #33362, #33433, #33576, #34374, #34450, #34481, #34500, #34502, #34510, #34511, #34539, #35567, #35564, #35485, #35380, #35063, #35060, #34676, #36917, #35337, #35520)
• Fragment Refs: Add Refs to <Fragment /> to support composable platform behavior (@​jackpope, @​sebmarkbage, @​eps1lon, @​Dhakshin2007, @​chirokas, @​teamleaderleo, @​fallintoplace: #32465, #32613, #32619, #32654, #32660, #32682, #32722, #32813, #32814, #33056, #33058, #33093, #34069, #34103, #34544, #34545, #37062, #37061, #37060, #36047, #36010, #35642, #35641, #35637, #35630, #34935, #37457, #37408, #37326, #37251, #37171, #37169, #37168, #37167, #37166, #37165, #37164, #37163, #37162,