From c472824ecc1dc782fa9722581f8f515fceb74327 Mon Sep 17 00:00:00 2001 From: only21mil Date: Sat, 31 Oct 2026 19:41:34 +0000 Subject: [PATCH] docs(mobile): Screens fork doc points at each archive's recorded source The doc linked the pingdotgg fork's t3-v5.0.0-t3.45 tag while the app ships 5.0.0-t3.48, whose source and tag live on the contributor fork named in its t3-fork.json. Link the fork itself and send readers to the repository and commit that t3-fork.json records, so the doc stays true across Screens bumps. Co-Authored-By: Claude Opus 5.5 --- docs/operations/mobile-screens-fork.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/operations/mobile-screens-fork.md b/docs/operations/mobile-screens-fork.md index b7b7454c94657..f6277973e808b 100644 --- a/docs/operations/mobile-screens-fork.md +++ b/docs/operations/mobile-screens-fork.md @@ -1,13 +1,15 @@ # Building the mobile Screens dependency The mobile v5 stack uses a committed tarball from the -[T3 Screens fork](https://github.com/pingdotgg/react-native-screens/tree/t3-v5.0.0-t3.45). +[T3 Screens fork](https://github.com/pingdotgg/react-native-screens). The fork owns the integration changes; the app does not patch this package. Each archive includes compiled JavaScript, declarations, native source and -`t3-fork.json` recording its version, source commit and upstream base. +`t3-fork.json` recording its source repository, version, source commit and +upstream base. To reproduce an archive, use Node 24 and the repository's pinned Yarn from a -clean fork checkout at the source commit recorded in its `t3-fork.json`: +clean checkout of the source repository and commit recorded in its +`t3-fork.json`: ```sh yarn --cwd /tmp/t3-screens-fork pack:t3 /absolute/path/to/t3code/apps/mobile/deps