From e0b5cab72d2c4f862f89d220ae607ed03de7df5b Mon Sep 17 00:00:00 2001 From: YamadaBlog Date: Sun, 14 Jun 2026 00:43:00 +0200 Subject: [PATCH] ci(publish): include react-native in the publish loop MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit react-native was bumped to rc.2 in the repo but the publish workflow's PKGS list omitted it, leaving repo=rc.2 / registry=rc.1 — the exact local/registry drift the audit flags. It ships source (no build), so it just publishes from its dir and gets provenance like the others. Co-Authored-By: Claude Fable 5 --- .github/workflows/publish-packages.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish-packages.yml b/.github/workflows/publish-packages.yml index f22388e..7e014ea 100644 --- a/.github/workflows/publish-packages.yml +++ b/.github/workflows/publish-packages.yml @@ -80,7 +80,9 @@ jobs: DIST_TAG: ${{ inputs.dist_tag }} run: | set -euo pipefail - PKGS="types tokens core web-component react svelte" + # react-native ships SOURCE (no build step) — it still + # publishes from its dir and gets provenance like the rest. + PKGS="types tokens core web-component react svelte react-native" for p in $PKGS; do dir="packages/$p" name=$(node -p "require('./$dir/package.json').name")