Release v0.2.0 - #374
Merged
Merged
Release v0.2.0#374
Conversation
Bump version.txt so the v0.2.0 tag and the APK it builds agree, and name the release in README and STATUS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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.



Bumps
version.txtfrom 0.1.1 to 0.2.0, so thev0.2.0tag and the APK it builds agree (release.ymlrefuses a tag that disagrees). README and STATUS name the release.Why 0.2.0: many new features and no breaking change to saved data.
Checks:
:app:assembleReleasepasses R8 locally;markdownLintandverifyDocsLinksare clean.After merge: I tag the merge commit
v0.2.0and push the tag. That runs the full check suite and publishes the signeddInfinityApp-0.2.0.apkwith its SHA-256.What's in it since v0.1.1
Based on
main(#373).🤖 Generated with Claude Code