Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Migrate to the new runtime-version macro #5395

Closed
pepyakin opened this issue Apr 26, 2022 · 2 comments · Fixed by #5402
Closed

Migrate to the new runtime-version macro #5395

pepyakin opened this issue Apr 26, 2022 · 2 comments · Fixed by #5402

Comments

@pepyakin
Copy link
Contributor

Currently, Polkadot, Kusama and other runtimes use an older way of declaring the runtime version:

// Polkadot version identifier;
/// Runtime version (Polkadot).
pub const VERSION: RuntimeVersion = RuntimeVersion {
spec_name: create_runtime_str!("polkadot"),
impl_name: create_runtime_str!("parity-polkadot"),
authoring_version: 0,
spec_version: 9190,
impl_version: 0,
#[cfg(not(feature = "disable-runtime-api"))]
apis: RUNTIME_API_VERSIONS,
#[cfg(feature = "disable-runtime-api")]
apis: version::create_apis_vec![[]],
transaction_version: 12,
state_version: 0,
};

In paritytech/substrate#7327 (PR paritytech/substrate#8688) Substrate changed the way runtime communicates the runtime version.

To complete this task, all the runtimes should migrate to the new runtime version specification mechanism. For the example, see the PR above here

@Doordashcon
Copy link
Contributor

entails majorly including the proc-macro in all runtimes?

@bkchr
Copy link
Member

bkchr commented Apr 27, 2022

Yes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants