chore(deps): bump @xmldom/xmldom, expo, expo-constants, expo-linking, expo-router, expo-splash-screen and jest-expo in /mqtt-client-React-Native-Expo

[dependabot]

Bumps @xmldom/xmldom to 0.8.15 and updates ancestor dependencies @xmldom/xmldom, expo, expo-constants, expo-linking, expo-router, expo-splash-screen and jest-expo. These dependencies need to be updated together.

Updates @xmldom/xmldom from 0.7.13 to 0.8.15

Release notes

Sourced from @​xmldom/xmldom's releases.

0.8.15

Commits

Fixed

• Security: parsing a deeply or repeatedly namespaced document no longer consumes quadratic memory; the in-scope namespace map is inherited through the prototype chain instead of being copied for every prefix-declaring element (O(N) instead of O(N²)), preventing a denial-of-service reachable from DOMParser.parseFromString with default options. Serialized output is byte-identical. GHSA-965w-775f-mr7g
• Security: attribute de-duplication during parsing is now O(M) instead of O(M²); the NamedNodeMap parse-time dedup path uses a null-prototype membership index, so a well-formed document with a hostile number of duplicate attributes can no longer wedge the parse. Attribute order and duplicate resolution (last value wins, first position kept) are byte-identical, preserving the XML no-duplicate-attributes well-formedness constraint. GHSA-8344-3jmq-59r6
• Security: trimming trailing whitespace from an XML end tag (ETag) is now anchored so it runs in linear time instead of backtracking quadratically on a long whitespace run, preventing a ReDoS reachable from DOMParser.parseFromString. Trimmed output is byte-identical. GHSA-x4fp-j954-r2f4
• Security: malformed-input recovery is now linear instead of quadratic — the malformed tag-name scan terminates at an embedded <, and Node.prototype.normalize() merges adjacent text nodes in O(K) instead of O(K²) (also reachable programmatically), per normalize() in the WHATWG DOM spec. DOM output is unchanged; only the reported error text differs. GHSA-93r5-fhx6-vmg9
• Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now rejects a DocType name that is not a valid XML Name, throwing InvalidStateError — matching the sibling publicId/systemId/internalSubset checks and preventing XML injection via DocumentType.name. GHSA-27p8-2357-5qqv
• Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now validates a processing-instruction target as an XML NCName and rejects a case-insensitive xml, throwing InvalidStateError — a check 0.8.x did not previously perform, preventing PI-target injection via >, ?, or whitespace. GHSA-c7q8-3ch8-vqpv
• Security: Document.createEntityReference() now rejects an invalid XML Name at creation, and XMLSerializer.serializeToString() under { requireWellFormed: true } validates an EntityReference nodeName as an XML Name, throwing InvalidStateError — preventing XML injection via an entity-reference name. GHSA-6gmq-8vp8-gcm6
• Security: the parser now reports a not-well-formed end tag whose valid name is followed by trailing content as a recoverable error instead of accepting it silently, per the XML ETag production; parsing recovers to the byte-identical DOM. Consumers that want strict rejection can escalate the reported error to fatal via the parser's errorHandler. GHSA-6h8r-xr42-gp59

Thank you, @​ericchiang, @​bhaswanthc, @​arpitjain099, @​Paranoidgrinch, for your contributions

0.8.14

Commits

Fixed

• Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm

Thank you, @​bhaswanthc, @​jmestwa-coder, for your contributions

0.8.13

Commits

Fixed

• Security: XMLSerializer.serializeToString() (and Node.toString(), NodeList.toString()) now accept a requireWellFormed option (fourth argument, after isHtml and nodeFilter). When { requireWellFormed: true } is passed, the serializer throws InvalidStateError for injection-prone node content, preventing XML injection via attacker-controlled node data. GHSA-j759-j44w-7fr8 GHSA-x6wf-f3px-wcqx GHSA-f6ww-3ggp-fr8h
  • Comment: throws when data contains -->
  • ProcessingInstruction: throws when data contains ?>
  • DocumentType: throws when publicId fails PubidLiteral, systemId fails SystemLiteral, or internalSubset contains ]>
• Security: DOM traversal operations (XMLSerializer.serializeToString(), Node.prototype.normalize(), Node.prototype.cloneNode(true), Document.prototype.importNode(node, true), node.textContent getter, getElementsByTagName() / getElementsByTagNameNS() / getElementsByClassName() / getElementById()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverable RangeError. GHSA-2v35-w6hq-6mfw

Thank you, @​Jvr2022, @​praveen-kv, @​TharVid, @​decsecre583, @​tlsbollei,

... (truncated)

Changelog

Sourced from @​xmldom/xmldom's changelog.

0.8.15

Fixed

• Security: parsing a deeply or repeatedly namespaced document no longer consumes quadratic memory; the in-scope namespace map is inherited through the prototype chain instead of being copied for every prefix-declaring element (O(N) instead of O(N²)), preventing a denial-of-service reachable from DOMParser.parseFromString with default options. Serialized output is byte-identical. GHSA-965w-775f-mr7g
• Security: attribute de-duplication during parsing is now O(M) instead of O(M²); the NamedNodeMap parse-time dedup path uses a null-prototype membership index, so a well-formed document with a hostile number of duplicate attributes can no longer wedge the parse. Attribute order and duplicate resolution (last value wins, first position kept) are byte-identical, preserving the XML no-duplicate-attributes well-formedness constraint. GHSA-8344-3jmq-59r6
• Security: trimming trailing whitespace from an XML end tag (ETag) is now anchored so it runs in linear time instead of backtracking quadratically on a long whitespace run, preventing a ReDoS reachable from DOMParser.parseFromString. Trimmed output is byte-identical. GHSA-x4fp-j954-r2f4
• Security: malformed-input recovery is now linear instead of quadratic — the malformed tag-name scan terminates at an embedded <, and Node.prototype.normalize() merges adjacent text nodes in O(K) instead of O(K²) (also reachable programmatically), per normalize() in the WHATWG DOM spec. DOM output is unchanged; only the reported error text differs. GHSA-93r5-fhx6-vmg9
• Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now rejects a DocType name that is not a valid XML Name, throwing InvalidStateError — matching the sibling publicId/systemId/internalSubset checks and preventing XML injection via DocumentType.name. GHSA-27p8-2357-5qqv
• Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now validates a processing-instruction target as an XML NCName and rejects a case-insensitive xml, throwing InvalidStateError — a check 0.8.x did not previously perform, preventing PI-target injection via >, ?, or whitespace. GHSA-c7q8-3ch8-vqpv
• Security: Document.createEntityReference() now rejects an invalid XML Name at creation, and XMLSerializer.serializeToString() under { requireWellFormed: true } validates an EntityReference nodeName as an XML Name, throwing InvalidStateError — preventing XML injection via an entity-reference name. GHSA-6gmq-8vp8-gcm6
• Security: the parser now reports a not-well-formed end tag whose valid name is followed by trailing content as a recoverable error instead of accepting it silently, per the XML ETag production; parsing recovers to the byte-identical DOM. Consumers that want strict rejection can escalate the reported error to fatal via the parser's errorHandler. GHSA-6h8r-xr42-gp59

Thank you, @​ericchiang, @​bhaswanthc, @​arpitjain099, @​Paranoidgrinch, for your contributions

0.9.11

Fixed

• Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm
• Security: the processing-instruction grammar regex no longer backtracks quadratically on an unterminated processing instruction (<?… with no closing ?>), preventing a denial-of-service (ReDoS) reachable from DOMParser.parseFromString with default options. GHSA-g53g-w8rj-fmg7
• CharacterData nodeValue and data are now kept in sync [#990](https://github.com/xmldom/xmldom/issues/990)

Chore

• updated dependencies

Thank you, @​bhaswanthc, @​jmestwa-coder, @​stevenobiajulu, for your contributions

0.8.14

Fixed

• Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm

Thank you, @​bhaswanthc, @​jmestwa-coder, for your contributions

0.9.10

... (truncated)

Commits

• b5b8fb5 0.8.15
• 327508e docs: add 0.8.15 CHANGELOG entry
• f40ccb8 fix: prevent quadratic malformed-tag recovery and normalize() adjacent-text m...
• 3abb093 fix: prevent end-tag whitespace-trim ReDoS via anchored trim (GHSA-x4fp-j954-...
• 2c548f2 fix: prevent quadratic attribute de-duplication via null-prototype membership...
• 08a74b4 test: characterize NamedNodeMap attribute de-duplication before the index ref...
• 954370f fix: prevent quadratic namespace-map memory consumption via prototype-chain i...
• 4430189 fix: report not-well-formed end-tag trailing content (GHSA-6h8r-xr42-gp59)
• 6c3fb5f fix: prevent XML injection via unsafe EntityReference name (GHSA-6gmq-8vp8-gcm6)
• 3b69487 fix: prevent XML injection via unsafe processing instruction target serializa...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by karfau, a new releaser for @​xmldom/xmldom since your current version.

Updates expo from 51.0.31 to 57.0.19

Changelog

Sourced from expo's changelog.

Changelog

Unpublished

🛠 Breaking changes

• Raise minimum Node.js version to ^22.13.0 (#47202 by @​kitten)

🎉 New features

🐛 Bug fixes

• [iOS] Fix a Hermes JSI crash during reloads where two overlapping RCTHost runtime callbacks shared EXReactNativeFactory's app context ivar, letting one callback decorate objects against the other callback's runtime. (#48576 by @​LizunovSergey)
• [iOS] Fix expo/fetch streaming race between URLSession delegate callbacks and startStreaming() that could deliver an empty body on a 200 response, drop chunks, or leave the body stream open. (#47796 by @​idoyana)
• Fix expo/fetch body-stream teardown races: aborting via an AbortSignal now rejects the in-flight read with an AbortError instead of hanging forever, and late native events no longer throw The stream is not in a state that permits enqueue/close from outside any consumer try/catch. (#47573 by @​idoyana)
• [iOS] Fix expo/fetch Response.text() and .arrayBuffer() never settling when the request fails (network drop, abort()) after the response was already delivered. (#48230 by @​zoontek)
• Fix iOS build against React Native 0.87+ by dropping the legacy architecture (bridge) RCTRootViewFactoryConfiguration setup. (#46641 by @​zoontek)
• Adopted the UIKit scene-based life cycle on iOS so apps built with the iOS 27 SDK launch correctly. (#46733 by @​alanjhughes)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in extensions. (#46799 by @​jakex7)
• [iOS] Fix Linking.getInitialURL() returning null and deep links being dropped when a URL cold-starts an app on the UIKit scene life cycle. (#47628 by @​tsapeta)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in iOSApplicationExtension for widgets. (#47894 by @​jakex7)
• [iOS] Add ExpoBundleConfiguration to derive RCTBundleConfiguration from the normalized bundle URL instead of default shared settings singleton (#48010 by @​kitten)
• [iOS] Resolve the dev server port from the RCTMetroPort Info.plist key at runtime so bare projects without expo-dev-client connect to their own Metro instance instead of defaulting to 8081. (#48098 by @​alanjhughes)
• Fix async imports (import(...)) via asyncRequireModule not a thenable instead of a full promise shape (#48550 by @​kitten)
• Fix window.location being called regardless of @expo/metro-runtime being present on native when an async chunk loads after Metro disconnects (#48944 by @​expo-bot)
• Fix DOM components dropping prop updates that are emitted while the WebView is still loading. (#48813 by @​expo-bot)
• Fix import.meta.url being null on web when transform.inlineRequires is enabled. (#49045 by @​expo-bot)
• Fix platform resolution of the expo/dom and expo/dom/internal subpath exports (#49056 by @​hassankhan)
• [iOS] Remove a duplicated ExpoModulesCore-Swift.h import block in ExpoReactNativeFactory.mm whose #else branch imported the header unconditionally, breaking builds where neither form is on the header search path. (#47729 by @​gabrieldonadel)

💡 Others

• Re-export useReleasingSharedObjectWithLifecycle from expo-modules-core. (#48819 by @​intergalacticspacehighway)
• [Android] ExpoReactHostFactory now passes host handlers' DevSupportManagerFactory to ReactHostImpl. (#47637 by @​alanjhughes)
• [macOS] Fix build by guarding the bundleConfiguration override, which requires react-native 0.84+. (#48494 by @​intergalacticspacehighway)
• Restore RCTHostRuntimeDelegate conformance for react-native-macos (#46420 by @​gabrieldonadel)
• Add explicit react-native/Libraries/Core/InitializeCore import to native runtime entrypoint (#46344 by @​kitten)
• [Internal] Update logbox imports (#46640 by @​kitten)
• Re-export more expo-modules-core APIs (#45987 by @​Wenszel)
• Update URL and URLSearchParams implementation to support IDNA/TR-46 and improve performance. Spec-adherence has increased and few gaps should now be noticeable compared to browsers (#47813 by @​kitten)
• [Internal] Add getBundleOrigin, exposed as expo/internal/bundle-origin (#48275 by @​kitten)
• [Internal] Derive getDevServer from the bundle URL internally and expose getBundleUrl helper (#48278 by @​kitten)
• Rewrite the TextDecoder implementation to increase decoding performance (#48877 by @​kitten)
• Bump to @expo/metro@56.0.2 and metro@0.84.5 (#49161 by @​kitten)

57.0.9 - 2026-07-29

This version does not introduce any user-facing changes.

57.0.8 - 2026-07-22

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo since your current version.

Updates expo-constants from 16.0.2 to 57.0.17

Changelog

Sourced from expo-constants's changelog.

Changelog

Unpublished

🛠 Breaking changes

🎉 New features

🐛 Bug fixes

• [iOS] Quote script-phase paths so iOS builds work from a project path containing a space. (#48747 by @​expo-bot)

💡 Others

57.0.8 - 2026-07-29

This version does not introduce any user-facing changes.

57.0.7 - 2026-07-22

This version does not introduce any user-facing changes.

57.0.6 - 2026-07-17

This version does not introduce any user-facing changes.

57.0.5 - 2026-07-15

This version does not introduce any user-facing changes.

57.0.4 - 2026-07-15

This version does not introduce any user-facing changes.

57.0.3 - 2026-07-03

This version does not introduce any user-facing changes.

57.0.2 - 2026-06-30

This version does not introduce any user-facing changes.

57.0.1 - 2026-06-27

This version does not introduce any user-facing changes.

57.0.0 - 2026-06-25

This version does not introduce any user-facing changes.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo-constants since your current version.

Updates expo-linking from 6.3.1 to 57.0.9

Changelog

Sourced from expo-linking's changelog.

Changelog

Unpublished

🛠 Breaking changes

🎉 New features

🐛 Bug fixes

• Create development deep links from the bundle URL's authority instead of the manifest's hostUri (#48275 by @​kitten)

💡 Others

• [Internal] Read the development server URL from expo/internal/bundle-origin instead of duplicating its accessor (#48278 by @​kitten)

57.0.4 - 2026-07-22

This version does not introduce any user-facing changes.

57.0.3 - 2026-07-15

This version does not introduce any user-facing changes.

57.0.2 - 2026-07-07

This version does not introduce any user-facing changes.

57.0.1 - 2026-06-30

This version does not introduce any user-facing changes.

57.0.0 - 2026-06-25

This version does not introduce any user-facing changes.

56.0.14 - 2026-06-10

This version does not introduce any user-facing changes.

56.0.13 - 2026-05-29

🎉 New features

• Added Linking.clearInitialURL() to reset the cached deep-link URL. (#46265 by @​gabrieldonadel)

56.0.12 — 2026-05-26

This version does not introduce any user-facing changes.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo-linking since your current version.

Updates expo-router from 3.5.23 to 57.0.18

Changelog

Sourced from expo-router's changelog.

Changelog

Unpublished

🛠 Breaking changes

• Remove UNSTABLE_UnhandledLinkingContext from expo-router/react-navigation. (#49616 by @​Ubax)
• Remove BaseNavigationContainer export from expo-router/react-navigation. (#49587 by @​Ubax)
• Dispatch queued navigation actions in React transitions. The current screen stays visible while the destination suspends, so SuspenseFallback no longer renders for navigation-triggered suspense. (#49448 by @​Ubax)
• Remove beforeRemove, __unsafe_action__, PreventRemoveContext, and usePreventRemoveContext from expo-router/react-navigation. (#49408 by @​Ubax)
• Preserve the focused route when switching navigator types in a conditional layout. (#49297 by @​Ubax)
• Generate deterministic navigation states and route keys. Complete states from custom routers or persisted state must include routeKeySeq. (#49297 by @​Ubax)
• Defer navigation.dispatch and navigation helper actions until after commit. Use navigation.dispatchSync for synchronous dispatch; dispatch functions are no longer supported. (#49297 by @​Ubax)
• Require complete state in CommonActions.reset and remove Router.getRehydratedState from expo-router/react-navigation. (#49297 by @​Ubax)
• Remove resetRoot from NavigationContainerRef and createNavigationContainerRef. (#49297 by @​Ubax)
• Remove NavigatorScreenParams, getActionFromState, and LinkingOptions.getActionFromState from expo-router/react-navigation. (#49297 by @​Ubax)
• Represent nested navigation only as navigation state. The screen, params, and initial params are now ordinary user params. (#49297 by @​Ubax)
• Stop copying ancestor route params into descendant routes during imperative navigation, matching cold-start deep-link behavior. (#49297 by @​Ubax)
• Custom routers must return { state, affectedRouteKey } from getStateForAction instead of returning navigation state directly. (#49297 by @​Ubax)
• The freezeOnBlur screen option is disabled and screens are never frozen when blurred. (#49163 by @​Ubax)
• Remove the experimental web modal implementation. See the web modals guide. (#49204 by @​Ubax)
• Remove NavigationIndependentTree and useNavigationIndependentTree from expo-router/react-navigation. To embed an isolated navigation tree in a screen, use @react-navigation/native. (#49172 by @​Ubax)
• Remove the deprecated Link and useLinkProps exports from expo-router/react-navigation. Use Link from expo-router with an href instead. (#48895 by @​Ubax)
• Remove the deprecated navigateDeprecated action and the navigationInChildEnabled container prop from expo-router/react-navigation. (#49102 by @​Ubax)
• Remove getInitialState from the Router interface. Custom routers no longer create initial state. (#48783 by @​Ubax)
• Remove routeParamList from RouterConfigOptions and remove the RouterActionOptions type. Custom routers receive RouterConfigOptions in getStateForAction. (#48783 by @​Ubax)
• Remove the deprecated NavigationContainer export (#48760 by @​Ubax)
• Remove the static default field from DrawerNavigationState and deprecate getDrawerStatusFromState. (#48750 by @​Ubax)
• Remove the preloadedRouteKeys field from TabNavigationState. (#48718 by @​Ubax)
• Make history optional in TabNavigationState and DrawerNavigationState (#48709 by @​Ubax)
• Make navigation state type optional for custom routers. (#48757 by @​Ubax)
• Handle PUSH in tab and drawer routers instead of coercing it to NAVIGATE. Custom routers must now handle the PUSH action in getStateForAction. (#48752 by @​Ubax)
• Remove the initialParams prop from Expo Router screens and routeParamList from custom router action options. (#48756 by @​Ubax)
• Remove the initialRouteName prop from Expo Router navigators. Configure the initial route with unstable_settings.initialRouteName in the route layout instead. (#48708 by @​Ubax)
• Remove NavigationContainerRefContext fallback in useNavigation. The hook now throws when called outside a navigator, including components rendered via ExpoRoot's wrapper prop. (#48638 by @​Ubax)
• Allow key to be undefined in the Descriptor type and in routes passed to screen options, navigator screenOptions, and RouteGroupConfig.screenOptions callbacks. (#48596 by @​Ubax)
• Unify JS Tabs, TopTabs, Drawer, and headless tabs with NativeTabs - only screens declared in the layout become visible. (#48499 by @​Ubax)
• Make href: null hide JS tabs and make their routes unreachable, redirecting navigation to the initial tab. (#48499 by @​Ubax)
• Remove getStateForRouteNamesChange from the Router interface on expo-router/react-navigation. Custom routers must handle the ROUTE_NAMES_CHANGED action in getStateForAction instead. (#48479 by @​Ubax)
• Migrate the JS TopTabs navigator to the standard-navigation integration. (#48498 by @​Ubax)
• Make beforeRemove non-preventable and add removePrevented event. (#48347 by @​Ubax)
• Remove the navigationKey prop from layout <Screen> and <Group> components. (#48502 by @​Ubax)
• Remove the redirect prop from layout <Screen> components. (#48369 by @​Ubax)
• Add redirectTo to protected routes and render guarded screens as redirects instead of removing them from navigators. (#47744 by @​Ubax)
• Migrate the Drawer navigator to the standard-navigation integration. (#47839 by @​Ubax)
• Remove StackNavigationState.preloadedRoutes property and append preloaded routes to state.routes (#47961 by @​Ubax)
• Migrate the JS Tabs navigator to the standard-navigation integration. (#48292 by @​Ubax)

🎉 New features

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo-router since your current version.

Updates expo-splash-screen from 0.27.5 to 57.0.8

Changelog

Sourced from expo-splash-screen's changelog.

Changelog

Unpublished

🛠 Breaking changes

🎉 New features

🐛 Bug fixes

• Generate a transparent Android splash drawable when the config plugin has no image. (#49371 by @​expo-tuft[bot])

💡 Others

57.0.5 - 2026-07-22

This version does not introduce any user-facing changes.

57.0.4 - 2026-07-15

This version does not introduce any user-facing changes.

57.0.3 - 2026-07-15

This version does not introduce any user-facing changes.

57.0.2 - 2026-07-03

This version does not introduce any user-facing changes.

57.0.1 - 2026-06-30

This version does not introduce any user-facing changes.

57.0.0 - 2026-06-25

This version does not introduce any user-facing changes.

56.0.10 — 2026-05-23

This version does not introduce any user-facing changes.

56.0.9 — 2026-05-20

This version does not introduce any user-facing changes.

56.0.8 — 2026-05-19

This version does not introduce any user-facing changes.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for expo-splash-screen since your current version.

Updates jest-expo from 51.0.4 to 57.0.5

Changelog

Sourced from jest-expo's changelog.

Changelog

This is the log of notable changes to the Expo client that are developer-facing. Package-specific changes not released in any SDK will be added here just before the release. Until then, you can find them in changelogs of the individual packages (see packages directory).

Unpublished

📚 3rd party library updates

🛠 Breaking changes

🎉 New features

🐛 Bug fixes

57.0.0 — 2026-07-08

🛠 Breaking changes

• @expo/ui
  • [universal][android] Use BasicTextField component instead of Filled Material TextField. (#46442 by @​nishan) (#46442 by @​intergalacticspacehighway)
• expo-modules-jsi
  • [iOS] JavaScriptError is now a copyable class conforming to Error (was a non-copyable struct), and JavaScriptValue no longer conforms to Error. (#47154 by @​tsapeta)
• expo-font
  • [web] Removed Server.resetServerContext(). Server-side font state is now scoped per-render via AsyncLocalStorage. (#46669 by @​hassankhan)
• @expo/cli
  • Make expo prebuild clear and regenerate the native folders by default. Pass --no-clean to apply changes to the existing folders instead. (#47209 by @​alanjhughes)

🎉 New features

• Initial release of @expo/require-utils 🥳
• pod-install
  • Support Bundler-managed CocoaPods installations (#43605 by @​tiwari91, @​kitten)
• @expo/ui
  • [iOS] Added the SwiftUI accessibilityHidden modifier to hide decorative views from VoiceOver and other assistive technologies during element traversal. (#46579 by @​ramonclaudio)
  • [iOS] Added the SwiftUI accessibilityIdentifier modifier to set a stable identifier for UI testing tools such as XCUITest. (#46556 by @​ramonclaudio)
  • [iOS] Added the SwiftUI dynamicTypeSize modifier to set or constrain the Dynamic Type size within a view. Accepts a single size or a { min, max } range, and cascades from <Host> to bound how far text scales at the largest accessibility sizes. (#46540 by @​ramonclaudio)
  • [iOS] Added children prop to Label component, allowing custom title views (e.g. a VStack with title and subtitle) while preserving native icon spacing and Dynamic Type icon sizing.
  • [iOS] Add buttonBorderShape SwiftUI modifier, which reshapes a styled button (for example a glass button) while preserving its native press effect. (#46348 by @​nishan) (#46348 by @​intergalacticspacehighway)
  • [jetpack-compose] Added NavigationBar and NavigationBarItem components.
  • [iOS] Added the SwiftUI listRowSpacing modifier. (#46417 by @​qiyangdev)
  • [iOS] Added support for custom SF Symbols in the SwiftUI Image component. (#46183 by @​cinques)
  • [swift-ui] Added <DisclosureGroup.Label> for custom label style. (#46288 by @​kudo)
  • [universal] Added <Collapsible.labelStyle> for custom label style. (#46288 by @​kudo)
  • [jetpack-compose] Added dropShadow and innerShadow modifiers. (#46364 by @​duyanhv)
  • [iOS] Added the SwiftUI imageScale modifier to scale SF Symbols within a view relative to the surrounding text (small, medium, large). (#46774 by @​ramonclaudio)
  • [jetpack-compose] Added onGloballyPositioned modifier, which reports a composable's window position and size. (#46744 by @​nishan) (#46744 by @​intergalacticspacehighway)
  • [iOS] Extended the SwiftUI onGeometryChange modifier to also report the view's global position (x/y) alongside its size. (#46744 by @​nishan) (#46744 by @​intergalacticspacehighway)
  • [iOS] Added the SwiftUI minimumScaleFactor modifier to let text shrink down to a given fraction of its size before truncating. (#46740 by @​nishan) (#46740 by @​intergalacticspacehighway)
  • [iOS][android] Added React Compiler-friendly get() / set() accessors to useNativeState, as an alternative to reading and writing .value. (#46690 by @​nishan) (#46692 by @​intergalacticspacehighway)

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alanhughes, a new releaser for jest-expo since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.