chore: release v0.1.7 - #19
Merged
Merged
Conversation
expo install --fix: bumps expo 57.0.7 -> ~57.0.8 (React 19.2.3 and React Native 0.86.0 stay at the SDK-57-blessed versions). Keeps the reference example app current. Not shipped in the npm tarball.
Maintenance release. No changes to the shipped runtime or public API. - Bump version to 0.1.7 (package.json, package-lock.json, ios/MyId.podspec, android/build.gradle) so the podspec/gradle pins track the package version for the native CI gates. - CHANGELOG: document the pre-publish tarball guard, the weekly SDK staleness check, and 100% CI-gated test coverage (all landed via PR #18). - README: strengthen the comparison-table status to "CI-gated 100% test coverage" to reflect the new coverage gate.
Tests previously ran as a step inside the combined 'Lint · Typecheck · Build · Test + coverage' job, so they had no distinct check line in the PR / Actions run. Promote them to a standalone 'Test + coverage' job so the run is visible on its own and executes in parallel with lint/build. The coverage threshold still gates it (and release.yml).
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.
Maintenance release v0.1.7. No changes to the shipped runtime or public API — it hardens the release pipeline, records the 100% CI-gated coverage from #18, and refreshes the reference example app.
Shipped in the npm tarball
package.json,package-lock.json,ios/MyId.podspec, andandroid/build.gradle(podspec/gradle track the package version so the native CI gates run on release PRs).[0.1.7]entry documenting the pre-publish tarball guard, the weekly SDK-staleness check, and 100% CI-gated test coverage.2026-07-22device-test date is unchanged — not re-run).Not shipped (housekeeping on
main)expo install --fix. React 19.2.3 / React Native 0.86.0 stay at the SDK-57-blessed versions (Expo's check flagged onlyexpo).Why a release with no runtime change
Everything in #18 (CI, tests, release scripts) lives outside the npm
filesallowlist, so it never reached consumers. This bumps the published version to record that hardening, refresh the "last published" freshness signal, and exercise the new tarball-guard + coverage gate end-to-end throughrelease.yml.Local verification
lint·typecheck·build·build:plugin·test:ci(106 tests, coverage gate met) ·verify-pack(36 files, 14/14 required, 0 forbidden) — all green. Version consistent 0.1.7 across pkg/lock/podspec/gradle.Tag
v0.1.7will be pushed after merge to trigger the OIDC publish.