Prepare for publishing the ReactAndroid AAR to jitpack.io

jitpack.yml

@@ -0,0 +1,29 @@
+# 1. Ask JitPack to activate OpenJDK 17 (it’s already in the image)
+jdk:
+  - openjdk17
+
+install:
+  # 2–5. Download Node 16.x, add to PATH, install Yarn, pull JS deps, then build
+  - |
+    # Use Node 16.x because its official Linux binaries target glibc ≥2.17,
+    # which matches JitPack’s container. Newer Node releases need glibc ≥2.27
+    # and will fail with “GLIBC_2.27 not found.”
+    NODE_VERSION=16.20.2
+    curl -fsSL https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION-linux-x64.tar.xz \
+      -o node.tar.xz
+
+    mkdir -p $HOME/node
+    tar -xJf node.tar.xz -C $HOME/node --strip-components=1
+    export PATH=$HOME/node/bin:$PATH
+
+    # We can’t use `apt-get install nodejs` here because JitPack’s builds
+    # run as a non-root user with no sudo—apt-get will hit permission errors.
+    # Bundling Node into our home directory is the only reliable approach.
+    npm install -g yarn
+
+    # Install JS dependencies per yarn.lock so any npx scripts in
+    # Settings.gradle.kts or build.gradle.kts can run successfully
+    yarn install --frozen-lockfile --ignore-engines
+
+    # Finally, run the ReactAndroid assemble
+    ./gradlew clean :packages:react-native:ReactAndroid:assembleRelease

packages/react-native/ReactAndroid/build.gradle.kts

@@ -720,5 +720,11 @@ apply(from = "./publish.gradle")
 // Please note that the original coordinates, `react-native`, have been voided
 // as they caused https://github.com/facebook/react-native/issues/35210
 publishing {
-  publications { getByName("release", MavenPublication::class) { artifactId = "react-android" } }
+  publications {
+    getByName("release", MavenPublication::class) {
+      artifactId = "react-android"
+      groupId = "com.github.isubscribed"
+      version = "0.79.2.1" // Bug fix for 0.79.2
+    }
+  }
 }