search

helikon-labs / substrate-simple-payout

Reward payout service for substrate-based chains.
GNU General Public License v3.0
11 stars 0 forks source link

Bump @polkadot/api from 11.2.1 to 12.0.2 #452

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps @polkadot/api from 11.2.1 to 12.0.2.

Release notes

Sourced from @​polkadot/api's releases.

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:

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:

  • Replace system_accountNextIndex with runtime api call accountNonceApi for api.derive.tx.signingInfo
  • Sanitize eras for api.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.
Changelog

Sourced from @​polkadot/api's changelog.

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:

12.0.1 June 24, 2024

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:

  • Replace system_accountNextIndex with runtime api call accountNonceApi for api.derive.tx.signingInfo
  • Sanitize eras for api.derive.staking._stakerRewards

11.3.1 June 17, 2024

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.
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 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] commented 4 months ago

Superseded by #454.