chore: bump rne to 0.9.0 and migrate to models.* accessor#19
Merged
Conversation
…essor - Bump peerDeps/devDeps to react-native-executorch ^0.9.0 and react-native-rag ^0.9.0 across workspaces; package version 0.9.0. - Migrate example app and READMEs from named model constants (ALL_MINILM_L6_V2, QWEN3_0_6B_QUANTIZED, ...) to the new typed models.* registry accessor recommended in rne 0.9.0. - Drop stale imports of symbols that were never exported by react-native-executorch (ALL_MINILM_L6_V2_TOKENIZER, LLAMA3_2_TOKENIZER, LLAMA3_2_1B_TOKENIZER, LLAMA3_2_TOKENIZER_CONFIG). - yarn.lock pins to 0.9.0-nightly-7b452e6-20260522 for local typecheck; regenerate against the published 0.9.0 release before publishing.
react-native-executorch 0.9.0 is not on npm yet (only nightlies), so ^0.9.0 has no resolution and `yarn install --immutable` fails in CI. Pin to 0.9.0-nightly-7b452e6-20260522 in the workspace and example package.json to unblock CI. Switch back to ^0.9.0 once the release is published.
Contributor
Author
|
TODO: Once RNE 0.9 lands, change pins from nightly to 0.9 |
12 tasks
react-native-executorch@0.9.0 and react-native-executorch-expo-resource-fetcher@0.9.0 are now on npm, so the temporary nightly pin can be reverted. Lockfile regenerated against the release.
chmjkb
approved these changes
May 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
react-native-executorch@^0.9.0andreact-native-rag@^0.9.0across all three workspaces; package version0.9.0.ALL_MINILM_L6_V2,QWEN3_0_6B_QUANTIZED, …) to the new typedmodels.*registry accessor introduced in rne 0.9.0.react-native-executorch(ALL_MINILM_L6_V2_TOKENIZER,LLAMA3_2_TOKENIZER,LLAMA3_2_1B_TOKENIZER,LLAMA3_2_TOKENIZER_CONFIG) — pre-existing README bugs.Compatibility audit
Audited every executorch API the adapter actually uses against the 0.9.0 source. Nothing the wrappers consume was broken:
TextEmbeddingsModule.fromCustomModel/forward/delete,LLMModule.fromCustomModel/configure/setTokenCallback/generate/interrupt/delete, and theChatConfig/Message/ResourceSourcetypes are all unchanged. Compatibility is structural; this PR is housekeeping.Before merging
yarn.lockhere pinsreact-native-executorch@0.9.0-nightly-7b452e6-20260522because that's what I typechecked against — 0.9.0 isn't on npm yet. Regenerate the lockfile against the published0.9.0release before the corresponding npm publish.