Repository navigation
Repair wp/5.8 branch Actions: Fetch react-native-screens as a pre-built tarball - #84445
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
38c171c to
b8e7bde
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
b8e7bde to
16e8cf9
Compare
ntsekouras
left a comment
There was a problem hiding this comment.
LGTM, thanks! npm ci now passes in every job, so JavaScript and All go green. Compressed Size and Admin 1-4 pass further up the stack.
16e8cf9 to
931945f
Compare
931945f to
76a63fc
Compare
Part of #82935.
What?
Changes the
react-native-screensdependency inpackages/react-native-editor/package.jsonfrom a git URL to a pre-built tarball, with the matchingpackage-lock.jsonentries:git+https://github.com/wordpress-mobile/react-native-screens.git#b3d907bda2695743f35fd874261dcd27e0912ecahttps://raw.githubusercontent.com/wordpress-mobile/react-native-screens/a25c3d81e0838d57c9f9ac77ef726751e329bad1/react-native-screens-2.9.0-wp-1.tgzWhy?
npm cifails in every CI job that installs dependencies, so nothing after it runs:For a git dependency, npm clones the repository and runs its
preparescript, herebob build, which runstsc:react-native-screensdoesn't pin@types/node, sotscgets the newest release from npm.typescriptrange (^3.8.3) resolves to TypeScript 3.9, which can't parse syntax from TypeScript 4.0–4.5 that current@types/nodeuses.tscfails withTS1005/TS1109/TS1110, and so doesnpm ci.A tarball already contains the built
lib/output, so npm doesn't runprepare.wp/5.9already uses this exact tarball.How?
The tarball is built from wordpress-mobile/react-native-screens@a25c3d8, a descendant of the commit this branch pinned (wordpress-mobile/react-native-screens@b3d907b).
src/is identical between the two commits. The only differences are Android/Gradle build files, the podspec, and the version string (2.9.0→2.9.0-wp-1), so this changes packaging, not behavior.lib/commonjs,lib/moduleandlib/typescriptalready built.integrityvalue inpackage-lock.jsonmatches the SHA-512 of the downloaded tarball, and the valuewp/5.9uses for the same file.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.