Repository navigation
Conversation
- Replace the kepler-ui-components EPG with KeplerEPG from @amazon-devices/keplerscript-epg - Update dependencies for RN 0.83 (React 19.2, TypeScript 5.8, @amazon-devices/react-native-kepler 4.0.0) - Replace Typography with Text and scale layout values by PixelRatio - Use @react-native/babel-preset and @react-native/typescript-config - Move ts-jest options inline and remove the duplicate jest.config.js - Set the manifest runtime-module to IReactNativeKepler_0 - Update README commands and links for the vega CLI, document KeplerEPG instead of the kepler-ui-components EPG, and match the prop and data types to the keplerscript-epg typings - Regenerate package-lock.json from registry.npmjs.org - Regenerate THIRD-PARTY-NOTICES for the production dependencies
State that release-rn-83 targets Vega OS 1.2 and point Vega OS 2.0 builds to the main branch.
Bring the release-rn-83 React Native 0.83 upgrade into main as a merge, so that later merges of release-rn-83 into main stay clean.
- Set [os.version] min and target to 2.0 in manifest.toml and drop the IVega_1_2 module from [needs] - Allow @amazon-devices/react-native-kepler ~4.0.0 instead of exactly 4.0.0, and refresh package-lock.json to 4.0.2 from registry.npmjs.org - Regenerate THIRD-PARTY-NOTICES for the production dependencies - Note in the README that the app needs Vega SDK 2.0 or later
Add a Branches section that lists main (React Native 0.83, Vega OS 2.0), release-rn-83 (React Native 0.83, Vega OS 1.2) and release-rn-72 (React Native 0.72, Vega OS 1.2), and a note in the prerequisites to check the branch and the Vega SDK version before building.
anishamalde
approved these changes
Nov 11, 2026
v7.2.0 predates React 18 and 19, so tests written against React 19.2 and react-test-renderer 19.2.0 would hit a peer conflict. v13.3.3 supports react and react-test-renderer >=18.2.0 and react-native >=0.71. v14 needs test-renderer 1.3, whose react-reconciler requires React ^19.3, while this app pins React 19.2.0. Regenerate package-lock.json from registry.npmjs.org.
Bring the @testing-library/react-native ^13.3.3 bump from the release-rn-83 PR into the main PR. package-lock.json had one adjacent-entry conflict (each side had removed different entries). It is resolved by keeping this branch's lockfile and applying the bump with npm install --package-lock-only.
Run a non-forced npm audit fix against registry.npmjs.org. Only package-lock.json changes: - minimatch 3.0.8 to 3.1.5 at the top level (and the nested 3.1.5 copies are deduplicated), which clears the high-severity ReDoS advisories for minimatch <=3.1.3 - @typescript-eslint packages 8.72.1 to 8.72.2 and brace-expansion 5.0.12 to 5.0.13 under @react-native/eslint-config (lint tooling) npm audit --omit=dev goes from 5 findings (1 high, 4 low) to 4 low.
Change @amazon-devices/react-native-kepler from exactly 4.0.0 to ~4.0.0, as on main, so it resolves 4.0.2. 4.0.0 pulls in @microsoft/api-extractor with vulnerable lodash, minimatch, ajv and @rushstack versions; 4.0.2 does not. Then run a non-forced npm audit fix against registry.npmjs.org (minimatch 3.0.8 to 3.1.5 and lint patch bumps). npm audit --omit=dev goes from 14 findings (4 high, 6 moderate, 4 low) to 4 low. package-lock.json now matches the vega-os-2.0 branch. Regenerate THIRD-PARTY-NOTICES for the production dependencies.
Bring the release-rn-83 security update into the main PR, so later merges of release-rn-83 into main stay clean. package.json and package-lock.json are already identical on both branches; the only change here is the regenerated THIRD-PARTY-NOTICES, which drops the minimatch 3.0.8 entry that npm audit fix removed.
On Vega OS 1.2 and 2.0 the system EPG component is built for React Native 0.72, so this React Native 0.83 build crashes on launch there. Point OS 1.2 and 2.0 users at release-rn-72, correct the release-rn-83 row (it currently holds the same React Native 0.72 code as release-rn-72), and explain that manifest.toml still declares 2.0 because the current Vega SDK does not accept 2.1 yet. Drop the hint to lower min to 1.2 on this branch.
# Conflicts: # package-lock.json
This commit goes on both PR #20 (head vega-rn-83, base release-rn-83) and PR #21 (head vega-os-2.0, base main) as a fast-forward of each head. Once both merge, release-rn-83 has the same code as main: React Native 0.83 and the Vega OS 2.0 manifest (min and target "2.0"). Update the Branches table row for release-rn-83 to say so: React Native 0.83, runs on Vega OS 2.1 or later like main, same code as main, prefer main. The "Check the branch first" note said other branches target an older OS, which is no longer true for release-rn-83; it now names release-rn-72. README only; no app file changes. Co-Authored-By: Claude <noreply@anthropic.com>
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
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
Moves
mainto React Native 0.83 and Vega OS 2.0, matching the branch layout of the other Vega samples.release-rn-83React Native 0.83 upgrade (vega-rn-83) intomain, so later merges fromrelease-rn-83stay clean.[os.version]minandtargetto2.0inmanifest.tomland removes theIVega_1_2module.mainVega OS 2.0,release-rn-83Vega OS 1.2,release-rn-72RN 0.72) and a "Check the branch first" note.Dependencies: the React Native 0.83 dependency set from
release-rn-83, with@amazon-devices/react-native-keplermoved to~4.0.0(4.0.2). The lockfile resolves from public npm only.Please merge the
release-rn-83PR first, then this PR, both with "Create a merge commit" (not squash), so future merges fromrelease-rn-83stay clean.Testing
main, the build fails becausehermescis not found.jest/globalsenvironment unknown, as on the currentmain) and type check (KeplerEPGRefnot exported bykeplerscript-epg2.8.9) fail; left for a follow-up.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.