8000 chore: prepare v0.1.0 build 18 for external TestFlight by shroominic · Pull Request #28 · shroominic/OpenGlucose · GitHub
[go: up one dir, main page]

Skip to content

chore: prepare v0.1.0 build 18 for external TestFlight - #28

Merged
shroominic merged 3 commits into
mainfrom
chore/testflight-external-build-18
Aug 14, 2026
Merged

shroominic merged 3 commits into
mainfrom
chore/testflight-external-build-18

Conversation

@shroominic
@shroominic shroominic commented Aug 13, 2026 •
Copy link
Copy Markdown
Owner

Summary

  • bump the Flutter app from 0.1.0+17 to 0.1.0+18
  • update the external TestFlight release-shell example and one-shot notification receipt path
  • align the v0.1.0 beta release notes with build 18
  • remove the unreviewed ITSAppUsesNonExemptEncryption=false declaration
  • require and document an explicit, recorded Account Holder export-compliance
    determination before external beta approval or tester notification

Why

Build 17 was exported as internal-only and cannot be promoted to external
TestFlight. External beta testing therefore requires a newly reviewed build
number from a clean source commit.

This PR only prepares committed release metadata. It does not mutate App Store
Connect or upload a build.

Validation

  • make check (full repository gate: tooling, formatting, analysis,
    unit/integration tests, Android and web builds, fail-closed Android signing
    check, unsigned iOS build, and native iOS tests)
  • focused flutter test --no-pub test/privacy_release_defaults_test.dart
  • plutil -lint openhealth/ios/Runner/Info.plist
  • audited all repository references to build 17; no stale build-specific
    references remain
  • git diff --check

@shroominic
shroominic merged commit 103aff6 into main Aug 14, 2026
9 checks passed
@shroominic
shroominic deleted the chore/testflight-external-build-18 branch August 14, 2026 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0