Bastian Köcher 26fa6e3c76 Move runtime upgrade to frame-executive (#5197) ...

* Move runtime upgrade to `frame-executive`

Instead of storing the runtime upgraded in the space of `frame-system`,
this moves it to `frame-executive`. We also start storing the
`spec_version` and `impl_version` the last runtime upgrade was applied.

This scheme has multiple advantages:
- We don't need to make sure that runtime upgrade was set.
- This will work in the future when we want to test a runtime upgrade,
because the `on_runtime_upgrade` will be executed automatically when the
runtime changes.

* Move `LAST_RUNTIME_UPGRADE` key to `frame-executive`

* Add some more documentation

* Make sure `spec_version` always increases between runtime upgrades

* Fix test

* Upgrade `parity-multiaddr` to fix compilation

* Also check if the `spec_name` changed

* Remove `RuntimeUpgraded` storage entry

* Don't run on genesis

2020-03-15 20:28:57 +01:00

..

client

Use CLI to configure max instances cache (#5177)

2020-03-11 09:43:37 +01:00

src

Move runtime upgrade to frame-executive (#5197)

2020-03-15 20:28:57 +01:00

transaction-pool

Don't remove invalid transactions when skipping. (#5121)

2020-03-05 17:00:31 +01:00

build.rs

WASM runtime switch to import memory (#4737)

2020-01-28 09:36:57 +01:00

Cargo.toml

removes use of sc_client::Client from node-transaction-factory (#5158)

2020-03-12 19:19:38 +01:00