ci: build RN playground APK on every release bump (#278)

* ci: build RN playground APK on every release bump

* ci: skip RN playground APK build when tag already exists

Guards the release-detection step against re-running on a commit whose
playground version was previously released — e.g., a re-release after a
revert. Without this, the workflow would rebuild the APK and fail when
uploading to an existing GitHub Release asset.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: wenfix

.github/workflows/build-rn-playground-apk.yml

@@ -131,9 +131,19 @@ jobs:
           TAG="${{ inputs.release_tag }}"
           APK="${{ steps.apk.outputs.apk_name }}"
 
+          # The RN playground is `"private": true` so our release tooling
+          # doesn't tag it the way it tags other workspaces. Create the tag
+          # on the release commit ourselves so the GitHub Release below has
+          # something to attach to.
+          if ! git rev-parse "refs/tags/$TAG" >/dev/null 2>&1; then
+            echo "Creating git tag $TAG at ${{ github.sha }}..."
+            git tag "$TAG" "${{ github.sha }}"
+            git push origin "refs/tags/$TAG"
+          fi
+
           # Ensure a GitHub Release exists for this tag (action-publish-release
-          # may only create one for the root monorepo tag). --notes-file /dev/null
-          # keeps it tidy; --verify-tag ensures the tag already exists in git.
+          # may only create one for the root monorepo tag). --verify-tag
+          # ensures the tag exists in git before we create the Release.
           if ! gh release view "$TAG" >/dev/null 2>&1; then
             echo "Creating GitHub Release for $TAG..."
             gh release create "$TAG" \

.github/workflows/publish-release.yml

@@ -107,20 +107,38 @@ jobs:
           PLAYGROUND_TAG="${PKG_NAME}@${PKG_VERSION}"
           echo "PLAYGROUND_TAG=$PLAYGROUND_TAG" >> "$GITHUB_OUTPUT"
 
-          # Check that the tag exists AND was created on this commit.
-          # A tag from a prior release would point to an older commit.
-          TAG_COMMIT=$(git rev-list -n 1 "refs/tags/$PLAYGROUND_TAG" 2>/dev/null || echo "")
-
-          if [ "$TAG_COMMIT" = "${{ github.sha }}" ]; then
-            echo "RELEASED=true" >> "$GITHUB_OUTPUT"
-            echo "$PLAYGROUND_TAG points to ${{ github.sha }} — released in this run"
+          # Detect a release by comparing the playground version against the
+          # parent commit. The RN playground is `"private": true` (so it is
+          # never npm-published), and our release tooling only tags
+          # non-private workspaces. We therefore can't rely on a per-package
+          # tag existing on the release commit the way we can for other
+          # workspaces — see build-rn-playground-apk.yml, which creates the
+          # tag itself when uploading the APK.
+          if git cat-file -e "${{ github.sha }}^:playground/react-native-playground/package.json" 2>/dev/null; then
+            git show "${{ github.sha }}^:playground/react-native-playground/package.json" > /tmp/prev-rn-pkg.json
+            PREV_VERSION=$(node -p "require('/tmp/prev-rn-pkg.json').version")
           else
-            echo "RELEASED=false" >> "$GITHUB_OUTPUT"
-            if [ -z "$TAG_COMMIT" ]; then
-              echo "$PLAYGROUND_TAG does not exist — playground was not released"
+            PREV_VERSION=""
+          fi
+
+          # Also skip if a tag for this version already exists. `git revert` of
+          # a release commit produces a "Revert ..." message that the
+          # IS_RELEASE filter (main.yml) rejects, so reverts never reach this
+          # step directly. But a release that re-uses a previously-tagged
+          # version (e.g., a re-release after a revert, or a workflow re-run)
+          # would otherwise rebuild the APK and fail when uploading to an
+          # existing release asset.
+          if [ -n "$PREV_VERSION" ] && [ "$PREV_VERSION" != "$PKG_VERSION" ]; then
+            if git rev-parse "refs/tags/$PLAYGROUND_TAG" >/dev/null 2>&1; then
+              echo "RELEASED=false" >> "$GITHUB_OUTPUT"
+              echo "$PLAYGROUND_TAG already exists in git — skipping APK build"
             else
-              echo "$PLAYGROUND_TAG points to $TAG_COMMIT, not ${{ github.sha }} — stale tag from a prior release"
+              echo "RELEASED=true" >> "$GITHUB_OUTPUT"
+              echo "$PKG_NAME bumped $PREV_VERSION -> $PKG_VERSION in ${{ github.sha }} — will build APK"
             fi
+          else
+            echo "RELEASED=false" >> "$GITHUB_OUTPUT"
+            echo "$PKG_NAME version unchanged at $PKG_VERSION — skipping APK build"
           fi
 
   publish-wagmi-to-gh-pages: