search

buidl-labs / polkaviz

Visualization efforts on the Polkadot Network!
https://polkavizproject.surge.sh/
2 stars 3 forks source link

Bump @polkadot/api from 1.12.2 to 1.34.1 in /polkaviz-app #156

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps @polkadot/api from 1.12.2 to 1.34.1.

Release notes

Sourced from @polkadot/api's releases.

v1.34.1

Upgrade priority: High. Metadata v12 is the next major version containing structural data exchange changes and will start rolling out to test and live networks in due course.

  • Breaking change The Decorated (from @polkadot/metadata) class signature has changed. It now always expects a valid Metadata object to be passed-in, instead of raw data. It is recommended to create a Metadata object, set it on the registry with .setMetadata and then only create a Decorated instance. (Only affects metadata-only users of the API)

Contributed:

Changes:

  • Ensure Metadata retrieval does not pollute the default registry
  • When passing { nonce: -1 } to signAndSend the API will use system.accountNextIndex to determine the nonce
  • Ensure that upgrades override old registry types (non-specified in current)
  • Support for Metadata v12 with fixed indices
  • Cleanups for WebSocket class detection and creation
  • Ensure that ignored map params yield an error on iterKey
  • Cater for older chains in derive democracy locks (availability detection)

v1.33.1

Upgrade priority: Low. Recommended when using clones instances.

Changes:

  • Allow paymentInfo on any extrinsic with tx.paymentInfo(<address>, <at>) (hash specified)
  • When cloning an API instance the runtimeChain is now properly set from source
  • When cloning an API instance the registry is shared with the source
  • Optimize derive receivedHeartbeats to not re-create the full object
  • Add staking.stakerPrefs derive to retrieve validatorPrefs over a range of eras
  • Basic map of Websocket error codes to short descriptions (where none available)

v1.32.1

Upgrade priority: Low. Recommended when manually using provider connect/disconnect or using multiple instances in a single process.

  • Breaking change Previously .isReady could throw an error, now it will always succeed on connection. For trapping errors, use the .isReadyOrError variant on the API
  • Breaking change The isConnected provider interface is now a getter, replacing previous calls to provider.isConnected(). Additionally the provider.disconnect() is now async, aligning with .connect().

Contributed:

Changes:

  • Adjust memoization to work on a per-instance basis, with no contamination between multiple api/provider instances
  • Added derive.chain.getBlock(hash) to retrieve a SignedBlock extended with an .author (same as derive.chain.getHeader(...))
  • Added api.{connect, disconnect}() as well as isConnected interfaces. The first functions async returning Promise<void>
  • Error on provider connections will now emit all (as expected) via the event emitter
  • Ensure that initial connection failures always retry (when using auto-connection management)
  • The api.derive.staking.query/queryMulti no longer retrieves session keys (can be done via .keys/keysMulti)
Changelog

Sourced from @polkadot/api's changelog.

1.34.1 Sep 21, 2020

Upgrade priority: High. Metadata v12 is the next major version containing structural data exchange changes and will start rolling out to test and live networks in due course.

  • Breaking change The Decorated (from @polkadot/metadata) class signature has changed. It now always expects a valid Metadata object to be passed-in, instead of raw data. It is recommended to create a Metadata object, set it on the registry with .setMetadata and then only create a Decorated instance. (Only affects metadata-only users of the API)

Contributed:

Changes:

  • Ensure Metadata retrieval does not pollute the default registry
  • When passing { nonce: -1 } to signAndSend the API will use system.accountNextIndex to determine the nonce
  • Ensure that upgrades override old registry types (non-specified in current)
  • Support for Metadata v12 with fixed indices
  • Cleanups for WebSocket class detection and creation
  • Ensure that ignored map params yield an error on iterKey
  • Cater for older chains in derive democracy locks (availability detection)

1.33.1 Sep 14, 2020

Upgrade priority: Low. Recommended when using clones instances.

Changes:

  • Allow paymentInfo on any extrinsic with tx.paymentInfo(<address>, <at>) (hash specified)
  • When cloning an API instance the runtimeChain is now properly set from source
  • When cloning an API instance the registry is shared with the source
  • Optimize derive receivedHeartbeats to not re-create the full object
  • Add staking.stakerPrefs derive to retrieve validatorPrefs over a range of eras
  • Basic map of Websocket error codes to short descriptions (where none available)

1.32.1 Sep 7, 2020

Upgrade priority: Low. Recommended when manually using provider connect/disconnect or using multiple instances in a single process.

  • Breaking change Previously .isReady could throw an error, now it will always succeed on connection. For trapping errors, use the .isReadyOrError variant on the API
  • Breaking change The isConnected provider interface is now a getter, replacing previous calls to provider.isConnected(). Additionally the provider.disconnect() is now async, aligning with .connect().

Contributed:

Changes:

  • Adjust memoization to work on a per-instance basis, with no contamination between multiple api/provider instances
Commits
Maintainer changes

This version was pushed to npm by polkadotjs, a new releaser for @polkadot/api since your current version.


Dependabot compatibility score

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)
dependabot-preview[bot] commented 4 years ago

Superseded by #161.