Update dependency @polkadot/api to v12 #233
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^11.3.1
->^12.0.2
Release Notes
polkadot-js/api (@polkadot/api)
v12.0.2
Compare Source
Important Changes:
withSignedTransaction
: This option has been added toSignerOptions
. When usingsignAndSend
,signAsync
, anddryRun
you may now enable or disable the use of thesignedTransaction
field by adding thewithSignedTransaction
option. When withSignedTransaction is not enabled but the signer adds a signedTransaction the api will error.signPayload
.withSignedTransaction
has also been added to theSignerPayload
type which allows forpayload.toPayload()
to include the option.signAsync
: now accepts thesignedTransaction
field as well. This means that ifwithSignedTransaction
is enabled, andsignedTransaction
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
Compare Source
Important Changes:
signedTransaction
field to theSignerResult
response for injected signers. This only applies to thesignPayload
method exposed in theSigner
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.mode
andmetadataHash
field for theCheckMetadataHash
signed extension.Changes:
system_accountNextIndex
with runtime api callaccountNonceApi
forapi.derive.tx.signingInfo
eras
forapi.derive.staking._stakerRewards
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.