v1.2.0 bump + Update Changelog #195
Merged
Conversation
This file contains 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
JSKitty
added
Documentation
JSKitty
added
Awaiting Review
|
Tested by 2 Quality Control members, not my preferred amount of tests, but... keeping on schedule. 🚀 |
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.
Abstract
This PR marks the release of v1.2.0, with a version bump and changelog update.
It also fixes a small handful of bugs: such as the Send UI confusing a Contact starting with "S" as a Cold Staking address, and also fixed the 'UI freeze' when a Cold Staking address was entered to the Send UI.
Testing
To test this PR, it's suggested to attempt these user flows, or variations of these:
This is just a few hours before the release of v1.2.0, so if there's a good time to catch last-minute bugs, that time is NOW! 💜
If any errors are found, the PR works unexpectedly, or you have viable suggestions to improve the UX or functionality of the PR, let me know!