Repository navigation
chore: release 0.1.0 - #28
Merged
Merged
Conversation
- `@cawrestler/react-native-duo/jest`: components render with the JS fallbacks; setMockDuoEnvironment / resetMockDuoEnvironment / createMockDuoEnvironment simulate Duo environments and update mounted providers. Fallbacks moved to src/fallback/ so the mock imports them without platform resolution picking the native `.ios` files. - docs/API_STABILITY.md: proposed stable/experimental classification and open naming questions for 0.1.0; @experimental JSDoc tags on the proposed experimental exports. - example/.maestro: arrangement switching, toolbar rail placement, and scene accessory registration flows (`yarn example e2e`). Duo Lab toggles now give their switches an accessibility label. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ability # Conflicts: # CHANGELOG.md # src/DuoSceneAccessory.tsx
…ments - RNDuoEnvironmentView on Android reads Jetpack WindowManager's FoldingFeature and the hinge-angle sensor and emits the same environment payload as iOS: hinge status/angle, the fold as a division (or occlusion) reserved region, geometry, window metrics, and size classes. isDuo and supportsDuoApis stay false. - DuoProvider uses the shared native provider on iOS and Android; the store exposes the provider host so descendants can map provider-local region frames. - The fallback DuoArrangementView splits its panes along an active fold (resolveFoldSplit), honoring `axes` and the hinge thickness. Verified on a Pixel Fold emulator (API 36): Hinge lab reports "Partially open 90.0°" with the hinge detected, and the fold arrives as an active division region. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md # src/fallback/DuoArrangementView.tsx
First stable release on npm `latest`. - package.json 0.1.0 with publishConfig.tag `latest`. - RELEASE_NOTES.md for 0.1.0: Android foldables, React accessory content, Jest mock, API stability, tested scope, known limitations. - CHANGELOG Unreleased -> 0.1.0. - API stability classification adopted; naming questions deferred as breaking changes. @experimental tags no longer reference 0.1.0. - README, CONTRIBUTING, COMPATIBILITY, and the Expo starter template install from `latest`; previews stay on `next`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release metadata for 0.1.0, the first stable release on npm
latest. There are no code changes beyond doc-comment wording.package.json:0.1.0, withpublishConfig.tagset tolatest.RELEASE_NOTES.md: rewritten for 0.1.0. Covers what's new since preview.2 (Android foldables, React content in accessories, the Jest mock, API stability labels, Maestro e2e), install steps, requirements, what was tested (CI, the iPhone Duo simulator, the Pixel Fold emulator) and known limitations (nothing verified on physical hardware).CHANGELOG.md:Unreleasedbecomes0.1.0 — 2026-10-08.docs/API_STABILITY.md: the classification is adopted, and the naming questions are recorded as deferred breaking changes. The@experimentaldoc comments no longer mention 0.1.0.latest; previews stay onnext.yarn validatepasses (77 Jest tests, 59 tooling tests). The package check confirmsRELEASE_NOTES.mdmatches0.1.0.After this merges and
mainCI passes, run the Publish npm workflow onmainwithdist_tag=latest. It publishes to npm and creates thev0.1.0tag and GitHub release.🤖 Generated with Claude Code