chore: prepare 1.0.0-beta.28 release - #179
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
enaboapps
marked this pull request as ready for review
September 15, 2026 08:25
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
2 participants
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.
Closes #178
Summary
Prepare 1.0.0-beta.28 for internal store distribution, carrying the restored Forwarding hold-to-stop for scanning profiles from #177. The version script updates the package identifier and the shared Android and iOS build ordinal from 29 to 30, preserving marketing version 1.0.0. Only
package.json,package-lock.jsonandapp.jsonchange.Validation
npm run validateon Node 24: lint, TypeScript, 594 tests across 66 suites, 21 of 21 Expo Doctor checksnpm run version:check: version metadata valid, 1.0.0-beta.28 build 30The user authorized merging this release preparation and publishing the prerelease through the documented Play internal and TestFlight workflows. Physical Android to PC scanning hold testing remains unverified.