-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.9.26 Dependency Upgrade #1699
Conversation
This is not true, current versions of |
@nazar-pc I had the same issue than the CI, which seems to be that cmake is installed but called with unknown argument |
Not really, we're building nodes in CI on Windows Server 2022, macOS 12 and Ubuntu 20.04, in all cases everything compiles just fine with default GitHub actions workers. Here is the latest run if you want to compare workflow file: https://github.com/subspace/subspace/actions/runs/2729396930
|
@nanocryk is it missing anything to merge ? |
Upgrade to substrate used in Polkadot 0.9.26 (#1691), and include all changes in our main dependencies.
Custom branches (with diffs from parity's branches) :
Runtime breaking changes
CheckAssociatedRelayNumber
inparachain-system
pallet. UsedRelayNumberStrictlyIncreases
like in all tests.Ensure relay chain block number strictly increases paritytech/cumulus#1280
SpendOrigin
intreasury
pallet. UsedNeverEnsureOrigin<Balance>
like in Polkadot and Kusama.Several tweaks needed for Governance 2.0 paritytech/substrate#11124
NetworkId
andJunction
now used bounded vecs. I updated our precompiles code to revert if the provided values are too long.Companion for paritytech/substrate#11631 paritytech/polkadot#5671
EnsureOneOf
=>EitherOfDiverse
(simple renaming)Client breaking changes
Refactoring
Left to do
remove_prefix
is deprecated. I changed it toclear_prefix
withu32::MAX
limit to keep the same behavior, but we should probably set a better limit.