Repository navigation
chore: prepare v0.1.0 beta release - #25
Merged
Merged
Conversation
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.
Summary
0.1.0+17and add truthful beta release notesINTERNETto the release manifest so the explicitly enabled BYO-key HTTPS integration works outside debug buildsRelease safety
v0.0.1+10APK is debug-signed and cannot be upgraded in place with the new dedicated beta certificateVerification
make check(all package/app tests, integration test, Android debug build, web build, iOS build, and native iOS tests)make tooling-check format-check lintflutter test --no-pub test/privacy_release_defaults_test.dartflutter build apk --release --no-pubcom.openglucose.app, version0.1.0build17, one non-debug signer, required permission, SHA-256582db2fb645a32c17f81c8705b488097fc0302931514d9c92d5f38a9421effa8Release operation after merge
Create and protect the
android-releaseenvironment, install the five signing secrets, protectv*tags, then publishv0.1.0as a prerelease. The workflow must build, attest, and attachopenglucose-0.1.0+17.apk; an assetless or failed prerelease must not be silently recreated or overwritten.