Releases: polkadot-js/api
Releases · polkadot-js/api
v12.0.2
Important Changes:
withSignedTransaction
: This option has been added toSignerOptions
. When usingsignAndSend
,signAsync
, anddryRun
you may now enable or disable the use of thesignedTransaction
field by adding thewithSignedTransaction
option. When withSignedTransaction is not enabled but the signer adds a signedTransaction the api will error.- Always disabled by default.
- This ensures no big breaking changes happen to the interface of
signPayload
. withSignedTransaction
has also been added to theSignerPayload
type which allows forpayload.toPayload()
to include the option.
signAsync
: now accepts thesignedTransaction
field as well. This means that ifwithSignedTransaction
is enabled, andsignedTransaction
is present the api will adjust the current payload attached to the SubmittableExtrinsic, and add the signature. Then the user can call.send()
as they please.dryRun
: All steps will be the same as signAsync with the exception that .send() has never needed to be called.
Contributed:
- Add LocationToAccountApi::convert_location runtime API (Thanks to https://github.com/bkontur)
v12.0.1
Important Changes:
- Addition of an optional
signedTransaction
field to theSignerResult
response for injected signers. This only applies to thesignPayload
method exposed in theSigner
interface for polkadot-js. As the name suggests the field expects a signed transaction (extrinsic) when inputted. When its present, the api will not add the signature to the payload, but instead broadcast the inputted signed transaction. This means the signer may modify the payload it's given. The only part of the payload that may not be modified is the call data. This is verified on the api, and will throw an error if it does not match the initial payloads call data.- This is very useful for signers that want to adjust the
mode
andmetadataHash
field for theCheckMetadataHash
signed extension. - Note that this is not your traditional breaking change since it more-so acts as an addition, but since this is a high magnitude change it is going to be considered a MAJOR bump.
- For more info please review the following PR (#5914)
- This is very useful for signers that want to adjust the
Changes:
- Replace
system_accountNextIndex
with runtime api callaccountNonceApi
forapi.derive.tx.signingInfo
- Sanitize
eras
forapi.derive.staking._stakerRewards
v11.3.1
Changes:
- Fix period assumption on signingInfo (derive)
- Bump dev to 0.79.3
- Update {Polkadot, Kusama, Westend} types-known
- Bump Substrate metadata to latest
- NOTE: Moving forward when bumping the metadata for {Polkadot, Kusama, Substrate} the version will
always be a minor bump since it can add, modify, remove augmented types.
- NOTE: Moving forward when bumping the metadata for {Polkadot, Kusama, Substrate} the version will
v11.2.1
Contributed:
- fix: Re-subscribe to chain updates on reconnection if not a clone (Thanks to https://github.com/F-OBrien)
Changes:
- Add support for AuraUnincludedSegmentApi (Thanks to https://github.com/bee344)
- Add support for ParachainHost v11 Api
- Update Kusama and Westend block upgrades
- Update Substrate metadata to latest
v11.1.1
Changes
- Dedupe nextElected accountIds in
api.derive.staking.nextElected
- Bump @polkadot/dev to 0.79.1 w/ topo sort
- Bump yarn to 4.2.2
- fix: updated extrinsics' assetId
toHuman
(Thanks to https://github.com/bee344) - fix
api.derive.accounts.{info && identity}
- feat: Add support for
CheckMetadataHash
signedExtension (Thanks to https://github.com/bee344)
v11.0.3
Changes
- Make
api.derive.staking.*
backwards compatible - Fix
claimedRewards
regression inapi.derive.staking.queryMulti
- Update Substrate to latest
v11.0.2
Changes
- Fix type for TAssetConversion in Polkadot Asset hub
v11.0.1
Breaking Changes:
Note! The following breaking changes only refer to @polkadot/api-derive
calls under api.derive.staking.*
due to the most recent breaking changes in runtime version v1.2. Please refer to the link next to the bullet points for more information.
- Update
api.derive.staking
calls with breaking changes (#5860) - Add
claimedRewardsEra
to api.derive.staking.query for compatibility with legacyClaimedRewards (#5862)
Contributed:
- Bump @substrate/connect to 0.8.10 (Thanks to https://github.com/kratico)
Changes:
- Update polkadot types-known for latest runtime upgrades
v10.13.1
Changes:
- Update CI actions and setup_node to v4
- Update substrate metadata to latest
- Support ParachainHost runtime api v6, 7, 8, 9, 10
- Resolve correct module for council derive
- Update westend types-known for 1010000
- Update kusama types-known for 1001003
v10.12.6
NOTE: Because of a broken CI build for 10.12.5 -> 10.12.6 is a replacement
Contributed:
- chore: fix typos in error (Thanks to https://github.com/xiaoxianBoy)
Changes:
- Upgrade westend types-known for 1009000
- Add
disableAscii
option for toHuman, and toPrimitive - V14 Update substrate latest metadata
- V15 Update substrate latest metadata
- Bump yarn to 4.1.1
- Add
assetId
getter field to to necessary ExtrinsicPayloads - Add Updated Runtime Defintions
- ValidateStatement
- MMRApi
- mmr_root
- mmr_leaf_count
- Core v5
- GenesisBuilder
- MixnetApi