Bump Rococo Runtime Spec Version #3171
Conversation
| @@ -150,7 +150,7 @@ pub const VERSION: RuntimeVersion = RuntimeVersion { | |||
| spec_name: create_runtime_str!("rococo"), | |||
| impl_name: create_runtime_str!("parity-rococo-v2.0"), | |||
| authoring_version: 0, | |||
| spec_version: 1_006_002, | |||
| spec_version: 1_006_003, | |||
There was a problem hiding this comment.
@EgorPopelyaev is this ok? or change to 1_700_000? 1.7.0 release was branched off yesterday, and if we need to release BridgeHubRococo from master
There was a problem hiding this comment.
1.7 would be on the release branch then, not master. I dont know if the runtimes from master should be used anywhere?
|
@alistair-singh what do you say we just wait for 1.7.0 release to come out (will be published over the weekend I believe) then just use that? in the meantime I believe you can re-initialize the Ethereum bridge without said fix - it'll be a problem only if we end up stalling BEEFY for multiple sessions before the 1.7.0 upgrade, which is unlikely
wdyt? |
|
I am happy to wait for 1.7. We can close this PR. If a stall happens before 1.7 is rolled out we can always re-initialize again. |
To deploy fix: #3108 and unblock the re-initialization of Ethereum bridge.