Releases: JoinColony/purser
v3.2.0
v3.1.1
v2.5.1
This PATCH
release of `purser' adds a workaround for an Infura issue (that becomes a problem with our MetaMask implementation) as documented here and more specifically here.
The gist of the change is that now, purser-metamask
has a workaround when using Infura
as a provider in order to correctly give metamask the type of response it expects (pending).
Thanks to @JamesLefrere for all the testing he needed to do in order to find this, and especially for fixing it!
Monorepo:
- Bumped version to next
PATCH
:2.5.1
purser-core:
purser-ledger:
- Use
purser-core
chain defaults internally, for all the chains #265 - Bumped version to next
PATCH
:1.4.1
purser-metamask:
- Added workaround for infura pending transactions #265
- Use
purser-core
chain defaults internally, for all the chains #265 - Bumped version to next
PATCH
:2.4.1
purser-software:
- Use
purser-core
chain defaults internally, for all the chains #265 - Bumped version to next
PATCH
:1.2.7
purser-trezor:
v2.5.0
This MINOR
release of purser
introduces basic support for chain definitions through the ethereumjs-common
package.
purser-core
now has an internal helper for dealing with this: getChainDefinition
, which in turn, is being used through the Ledger, Trezor and MetaMask packages.
This basically adds in support for custom chains. It's still pretty basic, as some chain IDs might fail ethereumjs-common
s internal validation, thus the transaction failing to sign.
Thanks again to @JamesLefrere for having to deal with all the ethereumjs-tx
changes and updates.
Monorepo:
purser-core:
- Added internal
getChainDefinition
helper #261 - Added
ethereumjs-common
as a direct dependency - Bumped version to next
MINOR
:2.2.0
purser-ledger:
- Updated dependencies:
- Added support for custom chain definitions through
purser-core
#261 - Bumped version to next
MINOR
:1.4.0
purser-metamask:
- Added support for custom chain definitions through
purser-core
#261 - Bumped version to next
MINOR
:2.4.0
purser-trezor:
v2.4.2
This is yet another PATCH release to address the changes in ethereumjs-tx
's version 2
, and how it deals, and expects the chainId
to be supplied to it.
This also improves the way the purser-core
package normalizes addresses, along with some minor, but welcomed flow type fixes.
Thanks again to @JamesLefrere for pushing this release forward!
Monorepo:
- Bumped version to next
PATCH
:2.4.2
purser-core:
purser-ledger:
- Fixed address normalization (based on the above
purser-core
changes, and passingchainId
to transactions #257 - Bumped version to next
PATCH
:1.3.2
purser-metamask:
- Fixed address normalization (based on the above
purser-core
changes, and passingchainId
to transactions #257 - Bumped version to next
PATCH
:2.3.3
purser-software:
purser-trezor:
v2.4.1
This is a PATCH release to hotfix the change in one of purser
's dependencies, which recently changed it's import signature: ethereumjs/ethereumjs-tx#159
This was an oversight when upgrading this dependency in release v2.3.0, as the unit test didn't catch due to the fact that we mock all external libraries when testing.
I guess this is making a case for integration tests.
Thanks to @JamesLefrere for this release as the quick turnaround!
Monorepo:
- Bumped version to next
PATCH
:2.4.1
purser-ledger:
purser-metamask:
purser-trezor:
v2.4.0
This MINOR release improves upon the changes of the previous one by making errors thrown by both purser-metamask
and purser-trezor
more robust.
In the case of purser-metamask
, it changes promise errors (ie: when a user cancels signing a transaction), to actually reject, so they can be caught outsite.
In the case of purser-trezor
it updates the static methods to be in line with the rest, and throw, rather then just log a console warning when a user cancels signing either a transaction or a message.
Thanks to @JamesLefrere for this release as he did all the work here!
Monorepo:
- Bumped version to next
MINOR
:2.4.0
purser-metamask:
- Refactor the static methods reject the promise when a user cancels a transaction #251
- Bumped version to next
PATCH
:2.3.1
purser-trezor:
v2.3.0
Besides a lot of dependency updates, the only actual change to the library is the way purser-metamask
handles user interactions when a transaction, or a message signing are being cancelled.
Previously this would fail silently by logging a warning to the browser's console.
The refactored version will throw an Error, on both cancelling a transaction and cancelling signing a message with the MetaMask wallet. See #246 for the details of this change.
Monorepo:
- Pinned dev dependencies versions:
- Updated dev dependencies:
- Bumped version to next
PATCH
:2.3.0
purser-core:
purser-ledger:
- Updated dependencies:
- Bumped version to next
MINOR
:1.3.0
purser-metamask:
- Updated dependencies:
- Refactor the static methods to throw when a user cancels a transactions (instead of just showing a warning) #246
- Bumped version to next
MINOR
:2.3.0
purser-software:
purser-trezor:
v2.2.0
This MINOR
release exposes a internal purser-metamask
's to the public namespace: accountChangeHook
. This is now available for direct import and it's to be used to hook a callback onto Metamask's State Event updates, so that you can act on wallet address changes from the UI.
Docs:
Monorepo:
- Updated dev dependencies:
- Bumped version to next
MINOR
:2.2.0
purser-metamask:
v2.1.1
This release is a hotfix, that pins the web3
package to version 1.0.0-beta.36
since that is the latest known beta version that will not break purser-metamask
's functionality.
Too see the debug chain that led to this change see the #197 issue and accompanying #202 PR.
Thanks to @fuguefoundation for finding this 🎉
Docs:
- Fixed a broken link to the
Flow
's typing system docs: #201 by @ceolson01
monorepo:
- Updated dev dependencies:
flow-bin
#201
- Fixed the
release-modules
script to properly pack modules when doing a dry run: 9583ed4 - Bumped version to next PATCH: 2.1.1
purser-metamask: