Release/0.8.4#199
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Release 0.8.4
Bumps all packages to
0.8.4and ships the bug fixes that landed since0.8.3. This is a fixes-only release — no new features.What changed
Top-up keys are now 64-byte sr25519 secret keys
If you fund a balance with
topUpusing acoinsorprivateKeysource, the keys are now 64-byte sr25519 secret keys (they were 32 bytes before). The call signature is unchanged — only the bytes you pass in differ.See the coin top-ups section of the migration guide.
Legacy account signing now works against the wallet
getLegacyAccountSignerwas sending a raw public key where the wallet expected an address, so signing requests could fail to match the account. It now sends the account's SS58 address, like the regular extension flow. No code change needed on your side.No more "Transport is disposed" errors on teardown
When a product was torn down, lingering subscriptions could still try to emit and throw
Transport is disposed. Subscriptions are now stopped cleanly when the transport is disposed.