-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade polkadot sdk #208
upgrade polkadot sdk #208
Conversation
…ule id correctly for ipfsKey
This PR updates the following pallets - they may also require updates to their extrinsic weights: For the author and any reviewers:
For a guide on running benchmarks to update weights see calculating weights |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to check version that is deployed is 1120 version
I've verified that the deployed version for prod is |
Pull Request
Checklist
PR Type
Please delete options that are irrelevant.
Linked tickets
https://digicatapult.atlassian.net/browse/SQNC-40
High level description
Upgrade polkadot-sdk to
stable2409-2
Detailed description
This upgrade includes the following changes:
stable2409-2
using https://github.com/paritytech/psvmscheduler
pallet to latestv3
api (the one we were using is deprecated)SymmetricKey
pallet to update the schedule id. This was changed in a previous release but never upgraded in this palletsqnc-node-runtime
tosqnc-runtime
2021
)sqnc-node
andsqnc-runtime
in line with changes tosolochain
template at this version of the sdkupdates weights for all pallets(done but run locally. See SQNC-69)I've also performed the following manual tests:
sqnc-matchmaker-api
onchain tests pass with this nodeDescribe alternatives you've considered
None
Operational impact
This update is a significant update to the Sequence node and runtime. Release will require first updating the node in produciton to this version and then the performing of a runtime upgrade. I would recommend a procudure like:
Note step 3 is irreversible except by rolling back the PVs to a backup.
Additional context
N/A