Skip to content

v1.9.2

Choose a tag to compare

View all tags
@BlackishGreen33 BlackishGreen33 released this 06 Jun 11:23
· 8 commits to main since this release
v1.9.2
bedc183

Highlights / 亮点

中文

  • v1.9.2 是 Third-party Native Wave A 的 stable release，发布到 npm latest，并保留 doctor --strict 只代表 verified 的公开边界。
  • 新增三项高频第三方 native blocker 的正式 telemetry：@react-native-async-storage/async-storage、react-native-screens、react-native-safe-area-context。
  • async-storage 与 react-native-screens 进入 experimental adapter slice，并分别要求 @react-native-oh-tpl/async-storage 与 @react-native-oh-tpl/react-native-screens 配对。
  • react-native-safe-area-context 进入 experimental shim slice，继续走 .expo-harmony/shims/react-native-safe-area-context Metro alias，不强行切到 native adapter。
  • 新增 Wave A fixture，覆盖 Expo SDK 55、RNOH 0.82.29、canonical package、adapter pairing、doctor 分类、telemetry、init / sync-template、bundle 与 debug-build 路径。

English

  • v1.9.2 is the stable Third-party Native Wave A release on npm latest, while preserving the public rule that doctor --strict only means verified support.
  • It formalizes telemetry for three frequent third-party native blockers: @react-native-async-storage/async-storage, react-native-screens, and react-native-safe-area-context.
  • async-storage and react-native-screens are now experimental adapter capabilities, paired with @react-native-oh-tpl/async-storage and @react-native-oh-tpl/react-native-screens.
  • react-native-safe-area-context is now an experimental shim capability and remains routed through .expo-harmony/shims/react-native-safe-area-context instead of forcing a native adapter.
  • A dedicated Wave A fixture covers Expo SDK 55, RNOH 0.82.29, canonical packages, adapter pairing, doctor classification, telemetry, init / sync-template, bundle, and debug-build paths.

Validation / 验证

中文

  • 本地验证：pnpm build。
  • 聚焦回归：pnpm exec jest --runInBand tests/doctor.test.ts tests/build.test.ts tests/docs.test.ts。
  • 文档同步与全量测试：pnpm docs:sync、pnpm test。
  • 发布前检查：git diff --check、EXPO_HARMONY_RELEASE_SKIP_HAP=1 pnpm release:check、npm pack --dry-run。
  • 远端验证：tag v1.9.2 触发的 GitHub release workflow 已成功，workflow run 27058065635。
  • npm 验证：latest -> 1.9.2，next -> 1.9.0 保持不变。

English

  • Local validation: pnpm build.
  • Focused regression: pnpm exec jest --runInBand tests/doctor.test.ts tests/build.test.ts tests/docs.test.ts.
  • Docs and full test sweep: pnpm docs:sync, pnpm test.
  • Release checks: git diff --check, EXPO_HARMONY_RELEASE_SKIP_HAP=1 pnpm release:check, and npm pack --dry-run.
  • Remote validation: the GitHub release workflow triggered by tag v1.9.2 completed successfully, workflow run 27058065635.
  • npm validation: latest -> 1.9.2; next -> 1.9.0 remains unchanged.

Notes / 说明

中文

  • doctor --strict 与 doctor --target-tier preview 仍会阻断 Wave A；只有 doctor --target-tier experimental 在 adapter 配对满足时允许通过。
  • 缺失 async-storage 或 screens adapter 时，会在双向配对关系上产生 dependency.required_missing 诊断。
  • Wave A 现在是 formal experimental onboarding，不是 verified promotion；真机、release HAP、真实持久化、navigation stack runtime 与 native inset measurement 仍需后续验收。
  • 本 release 补齐 GitHub Release 页面，作为 tag / npm trusted publishing 之外的人工可读发布记录。

English

  • doctor --strict and doctor --target-tier preview still block Wave A; only doctor --target-tier experimental allows it when adapter pairing is satisfied.
  • Missing async-storage or screens adapters emit dependency.required_missing diagnostics in both pairing directions.
  • Wave A is formal experimental onboarding, not verified promotion; true-device, release HAP, persistence behavior, navigation-stack runtime, and native inset measurement still need follow-up acceptance.
  • This release page fills the human-readable GitHub Release record in addition to the tag-driven npm trusted publishing path.
Assets 2
Loading