[dependabot]

Bumps the dependencies group with 9 updates:

Package	From	To
expo-dev-client	58.0.16	58.0.17
expo-image	58.0.17	58.0.18
expo-notifications	58.1.6	58.1.7
i18next	26.5.11	26.5.12
react-native-qrcode-svg	6.3.44	6.3.49
react-native-screens	4.30.0	4.30.1
@expo/cli	58.1.16	58.1.17
jest-expo	58.0.12	58.0.13
@types/node	26.6.5	26.6.6

Updates expo-dev-client from 58.0.16 to 58.0.17

Release notes

Sourced from expo-dev-client's releases.

expo-dev-client@58.0.17

Patch Changes

• Updated dependencies. (#52430)
  • expo-dev-launcher@58.0.17

Commits

• 2256296 refactor: Update tsconfig.json / tsc practices and Jest runners (composites...
• See full diff in compare view

Updates expo-image from 58.0.17 to 58.0.18

Release notes

Sourced from expo-image's releases.

expo-image@58.0.18

Patch Changes

• Rebuild precompiled iOS binaries against React Native 0.88.1. (#52404 by @​intergalacticspacehighway)

Changelog

Sourced from expo-image's changelog.

58.0.18

Patch Changes

• Rebuild precompiled iOS binaries against React Native 0.88.1. (#52404 by @​intergalacticspacehighway)

Commits

• 075c93f Version packages (sdk-58) (#52382)
• See full diff in compare view

Updates expo-notifications from 58.1.6 to 58.1.7

Release notes

Sourced from expo-notifications's releases.

expo-notifications@58.1.7

Patch Changes

• [Android] Fix importing expo-notifications throwing Cannot find native module 'ExpoTopicSubscriptionModule' in Expo Go. (#52182 by @​fixfon)
• Updated dependencies.
  • expo-constants@58.0.14
  • @​expo/image-utils@​0.12.6

Changelog

Sourced from expo-notifications's changelog.

58.1.7

Patch Changes

• [Android] Fix importing expo-notifications throwing Cannot find native module 'ExpoTopicSubscriptionModule' in Expo Go. (#52182 by @​fixfon)
• Updated dependencies.
  • expo-constants@58.0.14
  • @​expo/image-utils@​0.12.6

Commits

• 075c93f Version packages (sdk-58) (#52382)
• f63adb0 [android][notifications] Do not crash on import when ExpoTopicSubscriptionMod...
• See full diff in compare view

Updates i18next from 26.5.11 to 26.5.12

Release notes

Sourced from i18next's releases.

v26.5.12

• fix: with keySeparator: false or a custom separator like '::', a nested interpolation value that is 0, false or '' is now inserted. 'You have {{stats.unread}} unread messages' with { stats: { unread: 0 } } kept the raw {{stats.unread}} placeholder (or became '' with skipOnVariables: false), also for formatted values like {{order.total, currency(USD)}} and for nested defaultVariables: a falsy value was looked up again with the configured separator, which does not split stats.unread. The default '.' separator was not affected. When the same name exists both nested and as a flat dotted key ({ a: { b: 0 }, 'a.b': 'flat' }), the nested 0, false or '' now wins, as a truthy one already did; a nested null still falls back to the flat key. Thanks @​nk-batman21 (#2464).
• fix: cloneInstance({ forkResourceStore: true }) no longer changes the options object it is given. It deleted forkResourceStore from it, so reusing the same object for a second clone silently shared the parent's resource store (adding a resource to that clone also changed the parent), and frozen options threw a TypeError. Clones without forkResourceStore are unchanged. Thanks @​edsonsims (#2463).
• perf(types): a selector t(($) => ...) (enableSelector: true / 'strict') no longer filters the whole namespace, and no longer does it again for every distinct context value. To drop keys without anything to select, the filtered type looked at the filtered keys of every nested object, down to the leaves, also for the branches the selector does not read. It now decides from the source value. With 10,000 keys in 100 groups, one call went from 3.3M type instantiations (1.7s) to 0.85M (0.8s), and ten calls with ten contexts from 21.7M (8.8s) to 1.05M (0.9s), on TypeScript 6. Selected values are unchanged for context, plural, ordinal, nested and array keys, with three side effects: a type error on a selector now shows the type as FilterKeysObject<{ ...source keys }, Context> instead of the filtered object, an object whose values are all null or undefined ({ x: null }) is kept as {} instead of being dropped, and a null key next to its plural forms (foo: null, foo_one, foo_other) is typed as the plural value instead of never. Thanks @​GabrielVooDB (#2462).

Changelog

Sourced from i18next's changelog.

26.5.12

• fix: with keySeparator: false or a custom separator like '::', a nested interpolation value that is 0, false or '' is now inserted. 'You have {{stats.unread}} unread messages' with { stats: { unread: 0 } } kept the raw {{stats.unread}} placeholder (or became '' with skipOnVariables: false), also for formatted values like {{order.total, currency(USD)}} and for nested defaultVariables: a falsy value was looked up again with the configured separator, which does not split stats.unread. The default '.' separator was not affected. When the same name exists both nested and as a flat dotted key ({ a: { b: 0 }, 'a.b': 'flat' }), the nested 0, false or '' now wins, as a truthy one already did; a nested null still falls back to the flat key. Thanks @​nk-batman21 (#2464).
• fix: cloneInstance({ forkResourceStore: true }) no longer changes the options object it is given. It deleted forkResourceStore from it, so reusing the same object for a second clone silently shared the parent's resource store (adding a resource to that clone also changed the parent), and frozen options threw a TypeError. Clones without forkResourceStore are unchanged. Thanks @​edsonsims (#2463).
• perf(types): a selector t(($) => ...) (enableSelector: true / 'strict') no longer filters the whole namespace, and no longer does it again for every distinct context value. To drop keys without anything to select, the filtered type looked at the filtered keys of every nested object, down to the leaves, also for the branches the selector does not read. It now decides from the source value. With 10,000 keys in 100 groups, one call went from 3.3M type instantiations (1.7s) to 0.85M (0.8s), and ten calls with ten contexts from 21.7M (8.8s) to 1.05M (0.9s), on TypeScript 6. Selected values are unchanged for context, plural, ordinal, nested and array keys, with three side effects: a type error on a selector now shows the type as FilterKeysObject<{ ...source keys }, Context> instead of the filtered object, an object whose values are all null or undefined ({ x: null }) is kept as {} instead of being dropped, and a null key next to its plural forms (foo: null, foo_one, foo_other) is typed as the plural value instead of never. Thanks @​GabrielVooDB (#2462).

Commits

• 83f35e4 26.5.12
• a2a354e build
• b6447c1 changelog for 26.5.12
• 8bab707 changelog for unreleased #2464
• 5c43d88 fix: a nested null interpolation value still falls back to a flat key
• 1b7b734 fix: keep nested 0, false and '' interpolation values with a custom keySepara...
• 4184f91 changelog for unreleased #2463
• 4af40e5 fix: preserve caller options when forking instances (#2463)
• 42af830 chore: update dev dependencies to clear the Dependabot alerts
• 39bdcfe perf(types): selector t() no longer filters the whole namespace (#2462)
• Additional commits viewable in compare view

Updates react-native-qrcode-svg from 6.3.44 to 6.3.49

Commits

• 029bc4e Update package.json version to 6.3.49
• 7450eb3 Update package-lock.json version to 6.3.49
• ceee188 Merge pull request #291 from Expensify/claude-bumpShellQuote
• 56c5e46 Update package.json version to 6.3.48
• 12d5277 Update package-lock.json version to 6.3.48
• 15fa678 Merge pull request #278 from Expensify/claude-bumpLodashTo4.18.1
• 0487d7b Merge main into claude-bumpShellQuote
• 6065f2b Update package.json version to 6.3.47
• bd3e10e Update package-lock.json version to 6.3.47
• 49a2926 Merge pull request #281 from Expensify/claude-bumpFlatted
• Additional commits viewable in compare view

Updates react-native-screens from 4.30.0 to 4.30.1

Release notes

Sourced from react-native-screens's releases.

4.30.1

What's changed

This patch release backports a set of iOS fixes. Tabs now render the tab bar on an iPhone Duo cold-launched while unfolded, and a detached UISearchTab no longer leaves the remaining tab titles truncated. In Stack v4, cancelling an interactive dismissal of a screen pushed with UIKit's zoom transition (e.g. expo-router's Link.AppleZoom) no longer leaves the navigation bar with alpha == 0, so the back button and header items stay visible. SplitView gains RNSNavigationItemCustomizerProtocol, which lets third-party solutions customize a column's navigationItem, and column navigation bars now have prefersLargeTitles enabled with the collapsed title shown by default.

✅ Improvements

• feat(iOS, SplitView): add RNSNavigationItemCustomizerProtocol so third-party solutions can customize a column's navigationItem (#5080)
• feat(iOS, SplitView): enable large titles by default for column navigation bars (#5081)

🐞 Bugfixes

• fix(iOS, Tabs): size the tab bar controller's view before attaching it so the tab bar shows on an unfolded iPhone Duo (#4990)
• fix(iOS, Tabs): set the UISearchTab title at creation to avoid truncated tab titles (#5057)
• fix(iOS, Stack v4): restore navigation bar alpha after a cancelled zoom dismissal (#5055)

Full Changelog: software-mansion/react-native-screens@4.30.0...4.30.1

Commits

• 9d7da8f release: 4.30.1 (#5101)
• 7f6abb5 fix: Correct example after backporting (#5099)
• d69e4ac feat(SplitView, iOS): enable large titles by default for column navigation ba...
• b4a4794 feat(SplitView, iOS): Add RNSNavigationItemCustomizerProtocol (#5080) (#5096)
• 6b0d844 fix(iOS, Stack v4): restore navigation bar alpha after a cancelled zoom dismi...
• 14a22c7 fix(iOS, Tabs): Set the UISearchTab title at creation (#5057) (#5094)
• 573ee95 fix(iOS, Tabs): size the tab bar controller's view before attaching it (#4990...
• See full diff in compare view

Updates @expo/cli from 58.1.16 to 58.1.17

Release notes

Sourced from @​expo/cli's releases.

@​expo/cli@​58.1.17

Patch Changes

• Upgrade React Native to 0.88.1. (#52404 by @​intergalacticspacehighway)
• Fix server stack traces in development pointing at the wrong source file on Node 24.22 and later. Server bundle source maps are now read before their temporary files are removed, and loader bundles are marked in their bundle URL so Metro symbolicates them against the right bundle. (#52102 by @​brentvatne)
• Fix npx expo start --localhost refusing connections on 127.0.0.1. (#52324 by @​ramonclaudio)
• Updated dependencies. (#52404, #52102, #52126, #52406)
  • @​expo/metro-config@​58.0.19
  • @​expo/prebuild-config@​58.0.17
  • @​expo/require-utils@​58.0.5
  • @​expo/config@​58.0.9
  • @​expo/config-plugins@​58.0.11
  • @​expo/image-utils@​0.12.6
  • @​expo/router-server@​58.0.19
  • @​expo/inline-modules@​0.2.8

Commits

• b835d8b Upgrade React Native to 0.88.1 (#52403)
• 142ce92 feat(cli): Add compile command (#51428)
• 657ec93 [cli] Fix server stack traces pointing at the wrong source on Node 24.22+ (#5...
• 9bd718d experiment(cli): Add OSC 7501 program status to prompts (#51289)
• d46b2d3 fix(cli): Listen on 127.0.0.1 when --localhost is passed (#52324)
• See full diff in compare view

Updates jest-expo from 58.0.12 to 58.0.13

Release notes

Sourced from jest-expo's releases.

jest-expo@58.0.13

Patch Changes

• Upgrade React Native to 0.88.1. (#52404 by @​intergalacticspacehighway)

Changelog

Sourced from jest-expo's changelog.

58.0.13

Patch Changes

• Upgrade React Native to 0.88.1. (#52404 by @​intergalacticspacehighway)

Commits

• 075c93f Version packages (sdk-58) (#52382)
• 5d72289 [SDK-58] Upgrade React Native to 0.88.1 (#52404)
• See full diff in compare view

Updates @types/node from 26.6.5 to 26.6.6

Commits

• See full diff in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions