sdk-js
sdk-js copied to clipboard
chore: release 0.34.1
Checklist
- [x] Publish rc -> https://www.npmjs.com/package/@kiltprotocol/sdk-js/v/0.35.0-rc.1
- [x] Unpublish/deprecate previous rc
- [x] Update metadata and type augmentation -> https://github.com/KILTprotocol/sdk-js/pull/821/commits/c72ba30741f226ebcedf1b9f29b8921493aef439
- [x] Cherry-pick https://github.com/KILTprotocol/sdk-js/pull/822
- [x] Review
- [x] Tag latest commit with
0.34.1-rc.1
-> https://github.com/KILTprotocol/sdk-js/tree/0.34.1-rc.1 - [x] Publish new rc -> https://www.npmjs.com/package/@kiltprotocol/sdk-js/v/0.34.1-rc.1
- [x] Run integration tests in dip-sdk using rc and
latest-develop
of peregrine and consumer-template - [ ] Release on Spiritnet
- [ ] Publish release
- [ ] Merge
@rflechtner our current release strategy do not capture this case when a feature is deployed on Peregrine and not on Spiritnet. Nevertheless, I don't see any blockers from making this a proper release. The new types and definitions will be in AT LEAST runtime 1.12, and also are not relevant if the runtime call is not present, which is the case for Spiritnet runtimes. Plus, leaving this as an rc will delay Sporran integration, which is a fundamental component for integrators to, well, start integrating.
Why would you not make this an official release?
0.35 has been released, so this will also have to change to the new version.
We migrated to a different repo and peer dependencies, this PR is not relevant anymore.