chore(0.83): sync 0.83.10 and backport RedBox 2.0

[Saad Najmi (Saadnajmi)]

Release stack — current coordination

Tracker: React Native macOS 0.83–0.87: PR stack and release tracker

• Position: 2 of 18.
• Current review base: 0.83-stable. Retarget dependent PRs as their predecessors merge, following the tracker.
• Dependencies / release order: shared fixes into main precede this release in the tracker.
• Next step: Publish and verify RNM 0.83.0 with RN 0.83.10; then continue with feat: merge 0.84-merge into main #3030.
• Submitted head: 3ccba22de3c8305b87d86dd6e7f311df289cf53f.

Validation status

The 0.83 candidate passed local consumer, type/API, and scoped native validation. Fresh CI and review remain required.

The five final release consumers passed 56 local checks; all ten approved tarball hashes and five read-only publication previews passed.
These results retain their recorded source-tree scope. Each PR's current Checks tab is authoritative for remote CI.
The 2026-09-21 synchronization preserved the previous head under backup/pre-release-sync-20260921-1447/<original-branch> in its source repository.

This coordination section supersedes earlier release-order and status notes below. The existing implementation description follows.

---

Summary

• sync the 0.83 stable line through React Native 0.83.10
• restore the RedBox 2.0 CoreModules files dropped during the stable merge resolution
• preserve the existing AppKit RedBox V1 behavior from feat(macos): port RedBox 2.0 to macOS (AppKit) #3027
• backport the production RCTUIKit compatibility primitives and RedBox 2.0 AppKit consumer from feat(macos): port RedBox 2.0 to AppKit via RCTUIKit compatibility primitives #3054

This is the single 0.83 stable-line PR for both the upstream sync and the effective RedBox 2.0/AppKit backport. It supersedes #3027.

Provenance

The four additive commits are stacked on the previously reviewed #3022 head:

1. restore the extracted upstream RedBox 2.0 CoreModules files
2. apply the focused AppKit V1 adaptation
3. add the production RCTUIKit table/label/button primitives
4. add the RedBox 2.0 AppKit consumer

The V1 adaptation is byte-identical to #3027. Every other changed implementation file is byte-identical to the reviewed #3054 production stack. Native RCTUITableView tests and their project wiring are intentionally excluded, matching the repository-owner review decision on #3056.

Validation

• RNTester macOS build passed (EXIT=0, ** BUILD SUCCEEDED **)
• all nine changed Objective-C/Objective-C++ implementations compiled
• RNTester-macOS linked, validated, and produced the app bundle
• zero compile or linker errors
• build log SHA-256: d7f6c18b7d570d06a79297c774e6343a92e178910374ea9ab5a99d8ac77aad4e
• immutable install, lint, format, and focused Jest passed
• TypeScript failures are pre-existing in files untouched by this PR; generated TypeScript is not configured on this stable branch
• RedBox 2.0 controller fork ratio remains the reviewed 842 / 144 / 16 total lines / fork lines / top-level macOS guards

manual macOS RedBox 2.0 OFF/ON verification OUTSTANDING; do not undraft until performed

The bounded manual attempt could not obtain a script URL in the DerivedData-built app even with Metro ready and serving the bundle, so no manual OFF or ON behavior item is claimed as passed.

[Saad Najmi (Saadnajmi)]

Note

🤖 OpenCode — This comment was generated by an AI coding agent (OpenCode) at Saad Najmi (@Saadnajmi)'s request. Every claim below was mechanically verified against the repo (patch-id matching plus content inspection), but please treat it as a starting point for review rather than ground truth. One row is explicitly marked unverified.

Commit-by-commit: does each local change also need to land on main?

This PR has 121 commits, but only 15 are local to the branch — the other 105 arrived via the merge of v0.83.10 (0191f94 merging ff4f96a).

Method: patch-id match of each local commit against the last 300 commits of main, then content inspection of every non-match.

#	Commit	Subject	Verdict
1	59b2ef1	chore(0.83): add minor version plan for 0.83.10 sync	🚫 0.83-only — superseded 1 commit later by e32ff69
2	e32ff69	chore(0.83): use changeset instead of nx version-plan	🚫 0.83-only — release artifact for this sync
3	ee926ab	fix(0.83): macOS build + ESLint regressions from 0.83.10 merge	🚫 N/A — RCTFrameTimingsObserver.mm does not exist on main
4	dbb0b39	fix(ci): derive react_native_version from react-native peer dep	🍒 Cherry-pick — main still has the buggy form
5	4972b56	fix(ci): install unpublished virtualized-lists in release-branch gates	🍒 Cherry-pick — main still does a single yarn pack
6	661fd61	fix(ci): ignore @react-native/tester in changesets	🍒 Cherry-pick — ⚠️ unverified, see below
7	2b8f46b	fix(macos): guard UIWindow dealloc in RCTDevLoadingView	⏭️ Already fixed forward at 0.86
8	7518263	fix(ci): fall back to origin remote in changesets base detection	🍒 Cherry-pick — live bug on main
9	7ee8719	fix(ci): force transitive virtualized-lists resolution in test-app	🍒 Cherry-pick
10	7684cf0	fix(ci): skip published-integration gates for a new minor's first release	🍒 Cherry-pick — inherited by future -stable branches
11	9b6277d	chore(0.83): use npm trusted publishing	✅ Already in main as b3a73ab (#3071)
12	8fb0a40	fix(0.83): point changesets baseBranch at 0.83-stable	🚫 0.83-only — would break main
13	51e83d4	fix: prevent dev loading view clipping (#3023)	✅ Already in main as 78f5b04
14	4f3275e	docs: update release process for Changesets (#3032)	✅ Already in main as cc5fac9
15	e063ce9	feat(rctuikit): Add RCTUITableView for RedboxV1 and RedboxV2 (#3056)	✅ Already in main as efb2eb5

Totals: 4 already in main · 6 to cherry-pick · 1 already fixed forward · 4 not applicable.

Notes on the non-obvious rows

Row 7 — 2b8f46b does not need to land on main. main has no dealloc method in RCTDevLoadingView.mm at all; it arrives from upstream in 0.83.10, so there is nothing to guard. Traced forward along the merge stack:

Branch	dealloc
main	absent
0.84-merge	absent
0.85-merge	absent
0.86-merge	present, already guarded
0.87-merge	present, already guarded

The problem first appears on our mainline at 0.86 and is already handled correctly there. No gap, no cherry-pick needed.

Row 8 — 7518263 is a real bug on main, not hygiene. main currently has:

const remote = (repoPath && remotes.match(...)?.[1]) ?? 'origin';

When the regex does not match, repoPath && … evaluates to ''. Since '' is not nullish, ?? never fires and remote becomes the empty string. The fix switches ?? to ||.

Row 12 — deliberately excluded. Cherry-picking the baseBranch change would point main's changesets at origin/0.83-stable. main must keep origin/main.

Row 6 — the one unverified claim. main has "ignore": [] and carries the same private @react-native/tester package (private: true, version 0.83.0-main), so this plausibly applies there too — but I could not prove main needs it without actually running changesets. Treat as a maybe.

Prepared follow-up

A branch of the 6 cherry-picks has been prepared locally on top of main (b3a73ab) — linear, zero conflicts, +59/−18 across 6 files. The four CI script/workflow files come out byte-identical to this PR's head; .changeset/config.json intentionally differs in exactly one line (baseBranch stays origin/main). Not yet pushed.

One thing to decide first

#3026 (chore: minimize the virtualized-lists fork) is open against main and touches the same dependency that rows 5 and 9 work around. If #3026 lands first, those two may become unnecessary or need rework — so these should be sequenced against it.

Unrelated observation

#3056 already landed RCTUITableView on main, and the file contents are byte-identical to the copy carried lower in the 0.84→0.87 merge stack. That means a future rebase onto current main will render those commits empty rather than conflicting — a clean outcome, but expect empty-commit warnings.