Release LeanTypeDual 0.2.0 - #129
Merged
Merged
Conversation
First release containing the LeanBitLab v4.0.3-v4.0.8 upstream layer. versionCode 4200 stays above the shipped 0.1.0/4100.
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
1 participant
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.
Cuts LeanTypeDual 0.2.0 (versionCode
4200), the first release containing the LeanBitLab v4.0.3-v4.0.8 upstream layer merged in #126.versionCode 4200stays above the shipped0.1.0/4100, so signed builds upgrade in place.docs/releasenote/release_notes_v0.2.0.mdandfastlane/.../4200.txt.Verification
assembleStandardfullDebugsucceeds; APK reports0.2.0, code4200, packagecom.asafmah.leantypedual.debug.:app:testOfflineRunTestsUnitTestreports 320 tests / 4 failures, all four the known Windows-onlyParserTestasset-ordering failures that pass on Linux CI.