Repository navigation
Conversation
chore(release): sync v2.4.0 production ancestry into develop
hotfix: back-merge native build repair v2.4.1
feat(release): lightweight Android and Windows packages in 2.5.0
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
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.
Promote UTHelper 2.5.0 from develop to main with a merge commit.
Ship the tested lightweight Android profile as a production-signed ARM64 compressed APK, retain a compressed universal compatibility APK, and enable the verified Windows package cleanup with high CAB compression. Coordinate architecture selection, universal fallback, exact ABI evidence, seven public assets and six checksum entries. Keep the existing signing identities, installed channels and interactive installers. iOS retains the unsigned device IPA model.
Validation: 1631 local source/extension tests passed, 25 skipped; Ruff passed. Topic PR #71 passed all required checks. Benchmarks include nine physical Android clean-install/login-UI/uninstall cycles, authenticated runtime checks on both ARM64 profiles, and 24 Windows MSI installation/activation cycles. The final protected release workflow must build, sign, verify and attest the exact 2.5.0 inventory before publication.
The owner authorized this release and retains the review exception/environment approvals previously granted in the release-maintenance chat. Required CI/security checks remain mandatory before merge. Tag only the resulting main commit after its checks pass; do not rewrite old releases. Historical Sentry release association has an expired token and is separate from native asset verification/publication.