ci(release): run native checks on next pushes

Author: iexitdev

.github/workflows/native-release.yml

@@ -2,6 +2,16 @@ name: Native Release Checks
 
 on:
   workflow_dispatch:
+  push:
+    branches:
+      - next
+    paths:
+      - .github/workflows/native-release.yml
+      - apps/expo-showcase/**
+      - package-lock.json
+      - package.json
+      - packages/**
+      - scripts/run-expo-native-release-check.mjs
   pull_request:
     paths:
       - .github/workflows/native-release.yml

docs/internal/completion-audit.md

@@ -48,7 +48,7 @@ Concrete success criteria:
 
 | Requirement                  | Missing evidence                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Why it matters                                                                                                                    |
 | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| Native release workflow      | Local iOS and Android release builds passed, and the recorder/checker require a run URL, commit, and iOS/Android artifact links before marking workflow evidence complete; no green native workflow artifact is recorded yet. A May 6, 2026 manual dispatch attempt failed because `native-release.yml` is only on `next`, while GitHub Actions exposes workflow dispatches from the default `master` branch.                                                                                                        | Required before production beta/RC confidence                                                                                     |
+| Native release workflow      | Local iOS and Android release builds passed, and the recorder/checker require a run URL, commit, and iOS/Android artifact links before marking workflow evidence complete; no green native workflow artifact is recorded yet. `native-release.yml` now runs on relevant `next` pushes and can be manually dispatched once the workflow exists on the default branch.                                                                                                                                                 | Required before production beta/RC confidence                                                                                     |
 | Native e2e/runtime QA        | iOS simulator and Android emulator launch smoke exist, and `docs/release/evidence/native-runtime-qa.json` records partial status. `docs/release/native-qa-checklists.md` provides row-by-row execution guidance. `docs/release/evidence/native-runtime-matrix.json` has 2 partial line-chart smoke rows and 14 pending page/platform rows                                                                                                                                                                            | Gestures, scroll conflicts, text rendering, and release behavior can differ on device                                             |
 | RN CLI native projects       | No generated RN CLI `ios/` or `android/` projects are checked in                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Source-level RN CLI example exists, but release-build evidence still requires native projects                                     |
 | Pro paid implementation      | H4 approved the Pro/free boundary, but `@chart-kit/pro` remains a preview registry/composition package without license enforcement, paid implementations, or runtime activation                                                                                                                                                                                                                                                                                                                                      | Required before selling or labeling Pro as a finished paid package                                                                |
@@ -68,7 +68,7 @@ Concrete success criteria:
 
 ## Recommended Next Decisions
 
-1. Merge or otherwise expose `.github/workflows/native-release.yml` on the default `master` branch, then run the native release workflow on the release candidate commit to turn local iOS/Android build evidence into CI artifact evidence.
+1. Run the native release workflow on the release candidate commit through a relevant `next` push or by exposing `.github/workflows/native-release.yml` on the default `master` branch for manual dispatch; use the resulting iOS/Android artifacts to turn local build evidence into CI artifact evidence.
 2. Add or repair the GitHub Actions `NPM_TOKEN` secret, make sure it can create and publish public packages under the npm `@chart-kit` scope, then rerun the publish workflow with npm dist-tag `next`; it should skip the already-published root package and publish the remaining scoped free packages.
 3. Run the native runtime, accessibility, performance, and Skia evidence matrices.
 4. If production beta is the target, prioritize native device QA and accessibility QA before adding more chart features.

docs/release/evidence/native-release-workflow.json

@@ -3,7 +3,7 @@
   "status": "partial",
   "requiredFor": ["H5", "H6"],
   "lastUpdated": "2026-05-06",
-  "summary": "iOS and Android release builds passed locally, but the native release workflow still needs a green run on the release candidate commit. Manual dispatch is currently blocked because native-release.yml is only on next and GitHub Actions can dispatch workflows only after the workflow exists on the default branch.",
+  "summary": "iOS and Android release builds passed locally, and native-release.yml can run on next pushes or manual dispatch once the workflow exists on the default branch. The native release workflow still needs a green run on the release candidate commit.",
   "completedEntries": [
     {
       "date": "2026-05-05",
@@ -21,8 +21,7 @@
     }
   ],
   "missingEvidence": [
-    "native-release.yml must exist on the default branch or be merged before manual workflow_dispatch is available",
-    "green native release workflow run on the release candidate commit",
+    "green native release workflow run on the release candidate commit through next push or manual workflow_dispatch",
     "archived iOS workflow artifact or log",
     "archived Android workflow artifact or log"
   ]

docs/release/known-issues.md

@@ -6,7 +6,7 @@ These are allowed only as explicit Developer Preview caveats. Anything in this f
 
 Android and iOS release-build checks are configured in `.github/workflows/native-release.yml` and can be run locally with `npm run native:release:android` and `npm run native:release:ios`. The Expo showcase also verifies web screenshots and can run on device through Expo Go or Expo dev targets.
 
-The iOS and Android release builds passed locally on May 5, 2026. Android used OpenJDK 17 plus the Homebrew Android command-line tools SDK (`/opt/homebrew/share/android-commandlinetools`) and completed `assembleRelease`. The release script now fails before prebuild when either Java or the Android SDK is missing. The remaining gap is CI evidence: production beta/RC should not count native release-build coverage as complete until the native workflow has a green run on the release candidate commit. A manual dispatch attempt on May 6, 2026 failed because `.github/workflows/native-release.yml` exists on `next` but not on the default `master` branch, so GitHub does not expose it as a dispatchable workflow yet. The structured status lives in [native-release-workflow.json](evidence/native-release-workflow.json), and the exact unblock path is documented in [native-workflow-runbook.md](native-workflow-runbook.md).
+The iOS and Android release builds passed locally on May 5, 2026. Android used OpenJDK 17 plus the Homebrew Android command-line tools SDK (`/opt/homebrew/share/android-commandlinetools`) and completed `assembleRelease`. The release script now fails before prebuild when either Java or the Android SDK is missing. The remaining gap is CI evidence: production beta/RC should not count native release-build coverage as complete until the native workflow has a green run on the release candidate commit. A manual dispatch attempt on May 6, 2026 failed because `.github/workflows/native-release.yml` exists on `next` but not on the default `master` branch, so GitHub does not expose it as a dispatchable workflow yet; the workflow can also run from relevant `next` pushes. The structured status lives in [native-release-workflow.json](evidence/native-release-workflow.json), and the exact unblock path is documented in [native-workflow-runbook.md](native-workflow-runbook.md).
 
 Impact: Developer Preview can be used for preview and API feedback, but production users should wait for green native workflow verification before treating v2 as stable.
 

docs/release/native-release-checks.md

@@ -36,7 +36,7 @@ The release-check script restores `apps/expo-showcase/app.json` and `apps/expo-s
 
 ## CI
 
-The `Native Release Checks` workflow runs Android and iOS release-build jobs separately. It is available through `workflow_dispatch` and also runs on pull requests that touch package source, the showcase app, package manifests, or the native-release script.
+The `Native Release Checks` workflow runs Android and iOS release-build jobs separately. It runs on relevant `next` pushes, is available through `workflow_dispatch` once the workflow file exists on the default branch, and also runs on pull requests that touch package source, the showcase app, package manifests, or the native-release script.
 
 Each workflow job writes native build output into `docs/release/artifacts/native-workflow/*-release.log` and uploads those logs as GitHub Actions artifacts. The Android job also uploads the generated release APK when present. These artifacts are the expected evidence source for clearing the native workflow blocker in the release gate.
 

docs/release/native-workflow-runbook.md

@@ -6,6 +6,8 @@ Status on May 6, 2026: native iOS and Android release builds passed locally, but
 
 GitHub Actions only exposes manually dispatched workflows after the workflow file exists on the repository default branch. The workflow file currently exists on `next`, while the repository default branch is `master`, so `workflow_dispatch` is not available yet for `.github/workflows/native-release.yml`.
 
+The workflow is also configured to run on relevant `next` pushes. Use that path when the workflow is not dispatchable from the UI yet.
+
 Do not mark the native workflow evidence complete until a green workflow run exists on the release-candidate commit and both platform artifacts are archived.
 
 ## Required Evidence
@@ -20,9 +22,18 @@ The release gate requires:
 
 Local release-build passes are useful smoke evidence, but they do not replace this workflow evidence for RC/stable.
 
+## Run From A `next` Push
+
+Push a release-candidate commit to `next` that touches the workflow, showcase, packages, lockfile, package metadata, or native release script paths covered by the workflow `push` trigger. Then watch the resulting workflow run:
+
+```sh
+gh run list --workflow native-release.yml --branch next --limit 5
+gh run watch <run-id> --exit-status
+```
+
 ## Make The Workflow Dispatchable
 
-Choose one of these owner-approved paths:
+For manual runs, choose one of these owner-approved paths:
 
 - Merge the workflow file into the default branch as part of the release branch process.
 - Temporarily add the workflow file to the default branch, then dispatch it against `next` or the release-candidate branch.

scripts/record-native-workflow-evidence.test.mjs

@@ -44,7 +44,7 @@ describe("native workflow evidence recorder", () => {
       status: "partial"
     });
     expect(evidence.missingEvidence).toContain(
-      "green native release workflow run on the release candidate commit"
+      "green native release workflow run on the release candidate commit through next push or manual workflow_dispatch"
     );
   });