Skip to content

Commit 50a3074

Browse files
iexitdeviexitdev
committed
docs(release): record native workflow dispatch blocker
1 parent f064ab6 commit 50a3074

3 files changed

Lines changed: 6 additions & 5 deletions

File tree

‎docs/internal/completion-audit.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Concrete success criteria:
4848

4949
| Requirement | Missing evidence | Why it matters |
5050
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
51-
| 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 | Required before production beta/RC confidence |
51+
| 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 |
5252
| 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 16 pending page/platform rows | Gestures, scroll conflicts, text rendering, and release behavior can differ on device |
5353
| 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 |
5454
| 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:
6868

6969
## Recommended Next Decisions
7070

71-
1. Run the native release workflow on the release candidate commit to turn local iOS/Android build evidence into CI artifact evidence.
71+
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.
7272
2. Fix npm `@chart-kit` scope/token access, 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.
7373
3. Run the native runtime, accessibility, performance, and Skia evidence matrices.
7474
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‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
"schemaVersion": 1,
33
"status": "partial",
44
"requiredFor": ["H5", "H6"],
5-
"lastUpdated": "2026-05-05",
6-
"summary": "iOS and Android release builds passed locally, but the native release workflow still needs a green run on the release candidate commit.",
5+
"lastUpdated": "2026-05-06",
6+
"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.",
77
"completedEntries": [
88
{
99
"date": "2026-05-05",
@@ -21,6 +21,7 @@
2121
}
2222
],
2323
"missingEvidence": [
24+
"native-release.yml must exist on the default branch or be merged before manual workflow_dispatch is available",
2425
"green native release workflow run on the release candidate commit",
2526
"archived iOS workflow artifact or log",
2627
"archived Android workflow artifact or log"

‎docs/release/known-issues.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ These are allowed only as explicit Developer Preview caveats. Anything in this f
66

77
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.
88

9-
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. The structured status lives in [native-release-workflow.json](evidence/native-release-workflow.json).
9+
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).
1010

1111
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.
1212

0 commit comments

Comments
 (0)