maxsam4 / fork-off-substrate

This script allows bootstrapping a new substrate chain with the current state of a live chain
MIT License
110 stars 65 forks source link

Bump @polkadot/api from 6.8.1 to 9.2.3 #121

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @polkadot/api from 6.8.1 to 9.2.3.

Release notes

Sourced from @​polkadot/api's releases.

v9.2.3

Contributed:

Changes:

  • Adjust StakingLedger with fallback for Kusama 1050 (2 different structures on-chain)
  • Remove TryRuntime state call definitions (only off-chain usage)
  • Update to latest Substrate, Polkadot & Kusama metadata

v9.2.2

Changes:

  • Replace rpc.payment.queryInfo usage with call.transactionPaymentApi.queryInfo
  • Ensure that api.call.* is decorated on historic blocks

v9.2.1

  • Important If using import { WellKnownChain } from '@polkadot/rpc-provider' it is recommended that you rather use ScProvider.WellKnownChain (the import may be dropped in a future major version)

Changes:

  • Don't assume non-empty path specifiers on portable variant/composites
  • Explicit param length checks for all generic portable overrides
  • Re-export ScProvider in @polkadot/api, aligning with {Http, Ws}Provider
  • Expose WellKnownChain as static on ScProvider.WellKnownChain
  • Checks for non-available interface types & runtime/rpc definitions
  • Ensure .entries/.keys arguments is less than map-entry query
  • Add Polkadot 9260 upgrade block
  • Add Westend 9271 upgrade block
  • Update to latest Substrate metadata

v9.1.1

Contributed:

Changes:

  • Add noInitWarn: boolean flag to API options, disabling runtime & RPC warnings
  • Only log missing runtime calls on new (detected) specVersion
  • Add shallow/one-blockHash cache for api.at(...) instances
  • Add Westend 9270 upgrade block
  • Update to latest Substrate, Polkadot & Kusama metadata

v9.0.1

  • Breaking change The decorated field getters on Struct were moved to the prototype class for performance reasons. While struct.<field> access still behaves in the same way, with the same results, this does mean that the prototype getters are not visible when doing an Object.keys(struct) or when doing an object spread.
  • Breaking change Deprecated interfaces have been removed including tx.sign(...) (use signAsync), Result.{is, as}Error (use {is, as}Err) as well as storage .range(...) operations.
  • Breaking change Deprecated interfaces on api-contract have been removed. Always ensure you pass an options object to construction and query methods.

... (truncated)

Changelog

Sourced from @​polkadot/api's changelog.

9.2.3 Aug 21, 2022

Contributed:

Changes:

  • Adjust StakingLedger with fallback for Kusama 1050 (2 different structures on-chain)
  • Remove TryRuntime state call definitions (only off-chain usage)
  • Update to latest Substrate, Polkadot & Kusama metadata

9.2.2 Aug 16, 2022

Changes:

  • Replace rpc.payment.queryInfo usage with call.transactionPaymentApi.queryInfo
  • Ensure that api.call.* is decorated on historic blocks

9.2.1 Aug 13, 2022

  • Important If using import { WellKnownChain } from '@polkadot/rpc-provider' it is recommended that you rather use ScProvider.WellKnownChain (the import may be dropped in a future major version)

Changes:

  • Don't assume non-empty path specifiers on portable variant/composites
  • Explicit param length checks for all generic portable overrides
  • Re-export ScProvider in @polkadot/api, aligning with {Http, Ws}Provider
  • Expose WellKnownChain as static on ScProvider.WellKnownChain
  • Checks for non-available interface types & runtime/rpc definitions
  • Ensure .entries/.keys arguments is less than map-entry query
  • Add Polkadot 9260 upgrade block
  • Add Westend 9271 upgrade block
  • Update to latest Substrate metadata

9.1.1 Aug 6, 2022

Contributed:

Changes:

  • Add noInitWarn: boolean flag to API options, disabling runtime & RPC warnings
  • Only log missing runtime calls on new (detected) specVersion
  • Add shallow/one-blockHash cache for api.at(...) instances

... (truncated)

Commits


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[bot] commented 2 years ago

Superseded by #122.