Upgrade priority: Medium if not already on at least 3.3.1. The next upgrade of Kusama/Polkadot requires it.
Breaking change To support chains with multiple tokens, such as bridges, the ChainProperties type now returns an array of tokens and decimals (instead of singular values) in the token{Decimals, Symbol} getters. Additionally, this means that the registry interfaces has been changes, to registry.chainDecimals: number[] and registry.chainTokens: string[]. Where used the [0] index will return the first value if only interested in a single, for a straight conversion.
Changes:
Allow for the detection of on-chain capabilities as available (e.g. AccountData, ValidatorPrefs)
Cater for multiple tokens and decimals in the chain the chain system.properties (as per the chain specification)
Add a instances: { [key]: [module1, module2] } definition in teh bundle types, allowing for multiple instances (e.g. Balances)
Adjust the api-derive for balances to retrieve values via instances as well as across multiple modules
Ensure all types are registered for all metadata typegen steps
Add rpc.payment.queryFeeDetails RPC endpoint
Update types & metadata to latest Substrate
Move the @polkadot/x-rxjs package into the common repo
Allow doc generation for errors/events (markdown outputs)
v3.5.1
Upgrade priority: Low. Recommended for parachain developers.
Important The default for Substrate on the Address types are MultiAddress. It is recommended that chains add explicit definitions for Address and LookupSource in their types, instead of relying on the API-defaults. A future update will swap the API defaults to align with Substrate.
Important Like the above changes in Substrate, the AccountInfo structure has also changed. It is recommended that chain developers explicitly add AccountInfo: 'AccountInfoWithRefCount' for the version with refCount on and AccountInfoWithProviders for the latest Substrate version. As per the above, the API defaults will be changed to align with Substrate.
Remove recursion in vector/struct U8a stream decoding
Availability of staking made optional in session length calcs (era does require it)
Updates to parachain types, ensuring it has coverage for all the latest
Update all Rococo types to the latest (session keys, session reports, parachain indexes)
Update known upgrade checkpoints fo WestEnd
Add types of the lottery module in Substrate
Add and extend types for the crowdloan module in Polkadot
Adjust node-template to default to MultiAddress on specVersion >= 100
v3.4.1
Upgrade priority: Low. Fixes for parachain types, .entries() (with no values) and event.is(...) checks, users of these interfaces will have benefit.
Breaking change The derive.chain.{getBlock, subscribeNewBlocks} now return SignedBlockExtended, all with the actual extrinsics and events mapped. Users of the latter interface should take note.
Upgrade priority: Medium if not already on at least 3.3.1. The next upgrade of Kusama/Polkadot requires it.
Breaking change To support chains with multiple tokens, such as bridges, the ChainProperties type now returns an array of tokens and decimals (instead of singular values) in the token{Decimals, Symbol} getters. Additionally, this means that the registry interfaces has been changes, to registry.chainDecimals: number[] and registry.chainTokens: string[]. Where used the [0] index will return the first value if only interested in a single, for a straight conversion.
Changes:
Allow for the detection of on-chain capabilities as available (e.g. AccountData, ValidatorPrefs)
Cater for multiple tokens and decimals in the chain the chain system.properties (as per the chain specification)
Add a instances: { [key]: [module1, module2] } definition in teh bundle types, allowing for multiple instances (e.g. Balances)
Adjust the api-derive for balances to retrieve values via instances as well as across multiple modules
Ensure all types are registered for all metadata typegen steps
Add rpc.payment.queryFeeDetails RPC endpoint
Update types & metadata to latest Substrate
Move the @polkadot/x-rxjs package into the common repo
Allow doc generation for errors/events (markdown outputs)
3.5.1 Jan 18, 2020
Upgrade priority: Low. Recommended for parachain developers.
Important The default for Substrate on the Address types are MultiAddress. It is recommended that chains add explicit definitions for Address and LookupSource in their types, instead of relying on the API-defaults. A future update will swap the API defaults to align with Substrate.
Important Like the above changes in Substrate, the AccountInfo structure has also changed. It is recommended that chain developers explicitly add AccountInfo: 'AccountInfoWithRefCount' for the version with refCount on and AccountInfoWithProviders for the latest Substrate version. As per the above, the API defaults will be changed to align with Substrate.
This version was pushed to npm by polkadotjs, a new releaser for @polkadot/api since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps @polkadot/api from 1.12.2 to 3.6.4.
Release notes
Sourced from
@polkadot/api's releases
.... (truncated)
Changelog
Sourced from
@polkadot/api's changelog
.... (truncated)
Commits
Maintainer changes
This version was pushed to npm by polkadotjs, a new releaser for @polkadot/api since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)