Upgrade Substrate to polkadot-sdk#1193
Conversation
|
Not sure about integration tests, but regular tests all succeeded for me locally, while CI seems to be broken here |
|
Hm, I somehow didn't notice #1165. Why not upgrading to latest version there though? |
I usually only update the substrate deps of frontier's master branch when the team releases a new version of polkadot. This can reduce maintenance work, and the master branch of substrate usually does not have good stability. |
|
It seems that polkadot is about to release v1.1.0, and then we can directly migrate to polkadot-sdk repo |
nazar-pc
force-pushed
the
upgade-substrate-old-repo
branch
3 times, most recently
from
597ceb2 to
7d90c6d
Compare
|
Rebased against newly merged PRs in |
nazar-pc
force-pushed
the
upgade-substrate-old-repo
branch
from
7d90c6d to
8a0da7d
Compare
nazar-pc
force-pushed
the
upgade-substrate-old-repo
branch
from
8a0da7d to
068cb2e
Compare
|
Fixed lints as well |
# Conflicts: # client/rpc/src/eth/execute.rs
# Conflicts: # Cargo.lock
nazar-pc
changed the title
|
Pulled current |
|
superseded by #1201 |
3 participants
This is a straightforward mechanical upgrade, nothing fancy here, mostly things were simplified a bit upstream.
The first step is to catch up with old repo, after this upgrade to
polkadot-sdkshould be much easier.