Bump @polkadot/api-base from 10.13.1 to 12.2.2

[dependabot[bot]]

Bumps @polkadot/api-base from 10.13.1 to 12.2.2.

Release notes

Sourced from @​polkadot/api-base's releases.

v12.2.2

Changes:

• Fix toHuman error on mode

v12.2.1

Changes:

• Bump polkadot/common to 13.0.2
  • This contains the latest changes to the Ledger interface in @polkadot/hw-ledger. For more info please see (13.0.1)
• Bump Substrate Metadata to Latest
  • This includes additions and removals to the api's type augmentation. For more info please see (#5936)
• Update Polkadot 1002006 types-known
• Bump yarn to 4.3.1

v12.1.1

Contributed:

• Implement xcm payment api (Thanks to https://github.com/girazoki)

Changes:

• Update Augmented types for polkadot 1002005
• Update Augmented types for kusama 1002006
  • Note: This removes type support for the Identity pallet for Kusama, and stateTrieMigration
• Update upgrade blocks for {Kusama, Polkadot}

v12.0.2

Important Changes:

• withSignedTransaction: This option has been added to SignerOptions. When using signAndSend, signAsync, and dryRun you may now enable or disable the use of the signedTransaction field by adding the withSignedTransaction 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 the SignerPayload type which allows for payload.toPayload() to include the option.
• signAsync: now accepts the signedTransaction field as well. This means that if withSignedTransaction is enabled, and signedTransaction 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 the SignerResult response for injected signers. This only applies to the signPayload method exposed in the Signer 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 and metadataHash field for the CheckMetadataHash 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)](polkadot-js/api#5914)

Changes:

... (truncated)

Changelog

Sourced from @​polkadot/api-base's changelog.

12.2.2 July 25, 2024

Changes:

• Fix toHuman error on mode

12.2.1 July 13, 2024

Changes:

• Bump polkadot/common to 13.0.2
  • This contains the latest changes to the Ledger interface in @polkadot/hw-ledger. For more info please see (13.0.1)
• Bump Substrate Metadata to Latest
  • This includes additions and removals to the api's type augmentation. For more info please see (#5936)
• Update Polkadot 1002006 types-known
• Bump yarn to 4.3.1

12.1.1 July 2, 2024

Contributed:

• Implement xcm payment api (Thanks to https://github.com/girazoki)

Changes:

• Update Augmented types for polkadot 1002005
• Update Augmented types for kusama 1002006
  • Note: This removes type support for the Identity pallet for Kusama, and stateTrieMigration
• Update upgrade blocks for {Kusama, Polkadot}

12.0.2 June 27, 2024

Important Changes:

• withSignedTransaction: This option has been added to SignerOptions. When using signAndSend, signAsync, and dryRun you may now enable or disable the use of the signedTransaction field by adding the withSignedTransaction 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 the SignerPayload type which allows for payload.toPayload() to include the option.
• signAsync: now accepts the signedTransaction field as well. This means that if withSignedTransaction is enabled, and signedTransaction 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)

12.0.1 June 24, 2024

... (truncated)

Commits

• b0b2145 [CI Skip] release/stable 12.2.2
• ab683fb 12.2.2 (#5943)
• bfb92e6 [CI Skip] bump/beta 12.2.2-0-x
• dac94c5 [CI Skip] release/stable 12.2.1
• 83204f1 12.2.1 (#5939)
• fe64733 [CI Skip] bump/beta 12.1.2-3-x
• 771d06b [CI Skip] bump/beta 12.1.2-2-x
• f92f2ea [CI Skip] bump/beta 12.1.2-1-x
• 0945d26 [CI Skip] bump/beta 12.1.2-0-x
• 3f38963 Bump common to 13.0.2 (#5935)
• Additional commits viewable in compare view

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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]]

Superseded by #194.