chore: release package (beta)

[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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@react-native-ama/animations@2.0.0-beta.2

Patch Changes

• Updated dependencies [e424ffc79bd9a497e743529e4bb5c7899572fe86]:
  • @react-native-ama/core@2.0.0-beta.2

@react-native-ama/bottom-sheet@2.0.0-beta.2

Patch Changes

• Updated dependencies [e424ffc79bd9a497e743529e4bb5c7899572fe86]:
  • @react-native-ama/core@2.0.0-beta.2

@react-native-ama/core@2.0.0-beta.2

Patch Changes

• fix: packaging bugs breaking real external installs (all pre-date this fix, invisible in the monorepo since the source files are always present on disk there regardless of npm's files allowlist): (#339)

  • Critical: the native module didn't work at all for any external consumer — ios/, android/, and expo-module.config.json were never listed in package.json's files array, so no native source and no Expo autolinking manifest were ever published. Consumers hit Error: Cannot find native module 'ReactNativeAma' at runtime, since there was nothing for Expo's autolinking to discover or compile in. Added all three to files (excluding local android/build Gradle artifacts via a !android/build negation).
  • Critical: once the native module could be found, calling AMAProvider/start() crashed the app on iOS with a JSI assertion failure (Assertion failed: (runtime.isArray(*this))). iOS's Function("start") declared its parameter as [Any] (array), but JS calls start({...}) with a single object — Android's equivalent already correctly declared Map<String, Any?>?. Fixed iOS to declare [String: Any]?, matching both Android and the rest of iOS's own functions (e.g. highlight's explicit typed params).
  • Metro bundling failed with Unable to resolve "./../../ama.config.json" for any consumer, since ama.config.json (the package's own bundled default config, required directly from src/internals/config.ts) was never listed in files either.
  • Editor autocomplete for imports from @react-native-ama/core didn't work in consuming projects, since the package relied entirely on the conditional exports map for type resolution with no top-level types field as a fallback — editors/tsconfigs that don't fully resolve conditional exports types couldn't find any type info at all. Added a top-level "types": "./dist/index.d.ts".

@react-native-ama/forms@2.0.0-beta.2

Patch Changes

• Updated dependencies [e424ffc79bd9a497e743529e4bb5c7899572fe86]:
  • @react-native-ama/core@2.0.0-beta.2

@react-native-ama/lists@2.0.0-beta.2

Patch Changes

• Updated dependencies [e424ffc79bd9a497e743529e4bb5c7899572fe86]:
  • @react-native-ama/core@2.0.0-beta.2

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
react-native-ama	Ready	Preview, Comment	Jul 13, 2026 1:32pm