chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

brownfield@6.0.1

Patch Changes

• Updated dependencies [79817d1, 69fe3e3]:
  • @callstack/brownfield-cli@6.0.1

@callstack/brownfield-navigation@6.0.1

Patch Changes

• Updated dependencies [79817d1, 69fe3e3]:
  • @callstack/brownfield-cli@6.0.1

@callstack/brownie@6.0.1

Patch Changes

• Updated dependencies [79817d1, 69fe3e3]:
  • @callstack/brownfield-cli@6.0.1

@callstack/brownfield-cli@6.0.1

Patch Changes

• #487 79817d1 Thanks @KisaneNeko! - Support Expo modules in React Native CLI apps. brownfield package:* no longer runs expo prebuild on projects with committed android/ and ios/ directories, which used to delete the brownfield library module. Prebuild now runs only when the native directory is missing or gitignored. If you commit the generated directories of an Expo app, run npx expo prebuild yourself after changing app.json or config plugins. create-react-native-brownfield now detects Expo and sets up the iOS framework to use the Expo runtime. On a re-run after adding Expo, it also raises an existing framework target to iOS 16.4.

  --use-prebuilt-expo now also turns Expo's precompiled modules on or off for pod install, and turns on Swift explicit modules so packaging works in projects that still carry the old SWIFT_ENABLE_EXPLICIT_MODULES = NO workaround. It defaults to building Expo from source when the app's React Native version doesn't match the one Expo's precompiled modules were built for.

  package:ios now copies the expo-image dependency XCFrameworks (SDWebImage and libavif) as real files instead of symlinks into node_modules, so the package works when moved to another machine.

  Re-running create-react-native-brownfield after pod install no longer adds a second Sources build phase to the framework target, which made the next pod install fail.

  The package:ios script that create-react-native-brownfield adds now passes --add-spm-package, so the iOS app adds one local Swift package instead of every XCFramework. Existing scripts aren't changed.

• #485 69fe3e3 Thanks @hurali97! - respect --destination in package:ios when merging XCFrameworks

@callstack/create-react-native-brownfield@6.0.1

Patch Changes

• #487 79817d1 Thanks @KisaneNeko! - Support Expo modules in React Native CLI apps. brownfield package:* no longer runs expo prebuild on projects with committed android/ and ios/ directories, which used to delete the brownfield library module. Prebuild now runs only when the native directory is missing or gitignored. If you commit the generated directories of an Expo app, run npx expo prebuild yourself after changing app.json or config plugins. create-react-native-brownfield now detects Expo and sets up the iOS framework to use the Expo runtime. On a re-run after adding Expo, it also raises an existing framework target to iOS 16.4.

  --use-prebuilt-expo now also turns Expo's precompiled modules on or off for pod install, and turns on Swift explicit modules so packaging works in projects that still carry the old SWIFT_ENABLE_EXPLICIT_MODULES = NO workaround. It defaults to building Expo from source when the app's React Native version doesn't match the one Expo's precompiled modules were built for.

  package:ios now copies the expo-image dependency XCFrameworks (SDWebImage and libavif) as real files instead of symlinks into node_modules, so the package works when moved to another machine.

  Re-running create-react-native-brownfield after pod install no longer adds a second Sources build phase to the framework target, which made the next pod install fail.

  The package:ios script that create-react-native-brownfield adds now passes --add-spm-package, so the iOS app adds one local Swift package instead of every XCFramework. Existing scripts aren't changed.

• Updated dependencies [79817d1, 0f62490]:

  • @callstack/react-native-brownfield@6.0.1

@callstack/react-native-brownfield@6.0.1

Patch Changes

• #487 79817d1 Thanks @KisaneNeko! - Support Expo modules in React Native CLI apps. brownfield package:* no longer runs expo prebuild on projects with committed android/ and ios/ directories, which used to delete the brownfield library module. Prebuild now runs only when the native directory is missing or gitignored. If you commit the generated directories of an Expo app, run npx expo prebuild yourself after changing app.json or config plugins. create-react-native-brownfield now detects Expo and sets up the iOS framework to use the Expo runtime. On a re-run after adding Expo, it also raises an existing framework target to iOS 16.4.

  --use-prebuilt-expo now also turns Expo's precompiled modules on or off for pod install, and turns on Swift explicit modules so packaging works in projects that still carry the old SWIFT_ENABLE_EXPLICIT_MODULES = NO workaround. It defaults to building Expo from source when the app's React Native version doesn't match the one Expo's precompiled modules were built for.

  package:ios now copies the expo-image dependency XCFrameworks (SDWebImage and libavif) as real files instead of symlinks into node_modules, so the package works when moved to another machine.

  Re-running create-react-native-brownfield after pod install no longer adds a second Sources build phase to the framework target, which made the next pod install fail.

  The package:ios script that create-react-native-brownfield adds now passes --add-spm-package, so the iOS app adds one local Swift package instead of every XCFramework. Existing scripts aren't changed.

• #500 0f62490 Thanks @hurali97! - fix(android): stop the scaffolded ReactNativeHostManager from loading React Native twice

  The ReactNativeHostManager.kt generated by npm create @callstack/react-native-brownfield for React Native CLI projects called loadReactNative(application) and then ReactNativeBrownfield.initialize(...). Both run DefaultNewArchitectureEntryPoint.load(), which overrides the React Native feature flags, so the app crashed on startup with Feature flags cannot be overridden more than once.

  The generated host manager now:

  • no longer calls loadReactNative (ReactNativeBrownfield.initialize already loads the native libraries and feature flags exactly once);
  • passes the ReactHost as a factory to the non-deprecated initialize overload, so it is built after SoLoader.init instead of crashing with SoLoader.init() not yet called;
  • keeps the one behavior loadReactNative provided on the side by flagging edge-to-edge when IS_EDGE_TO_EDGE_ENABLED is set.

  Fixes #492.

• Updated dependencies [79817d1, 69fe3e3]:

  • @callstack/brownfield-cli@6.0.1