chore: use api v15 #945
Open
chore: use api v15 #945
+350
−347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We have the opportunity to bump pjs dependencies on the v0 branch to v15 (v13 for
commonpackages) before the release of 0.36.0, which would give us a@polkadot/apiversion with support for metadata v15. This eliminates the need for updates to the type-definitions package, and thus does away with having to bump these in all apps whenever a new runtime api version is released.So far we planned to release with v11, which is the minimum version compatible with the new runtime, but this seems short-sighted; I'm sure that now that an sdk upgrade is required to support the new runtime, people would prefer to update once and be done with it for the near future, instead of having to make package bumps again when we make changes to runtime apis.