Repository navigation
chore: release 0.2.0 - #16
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
Moves the entries added since
v0.1.0under## 0.2.0and puts the older ones under a new## 0.1.0heading.v0.1.0shipped with everything under Unreleased.After merging, tagging
v0.2.0makesrelease.ymlbuild the signed APK (versionName0.2.0, versionCode200) and publish the GitHub release.Why
0.2.0 ships the voice gateway call UI and the removal of server configuration from the app (#14). That needs bot 0.7.0 on the server for the calls.
Evidence
Changelog-only change. CI on #14 and #13 passed. #15 (CI change) can merge before or after this.
Risk & Rollback
Reversibility: Reversible until the tag is pushed. A published release can be deleted but may already be downloaded.
Blast Radius:
CHANGELOG.mdonly.