🙈 Fix paseo chain spec files files #340
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @JuaniRios and the rest of your teammates on |
JuaniRios
force-pushed
the
06-26-new_paseo_binaries
branch
2 times, most recently
from
941123c
to
4fdc7af
Compare
lrazovic
approved these changes
Jun 27, 2024
JuaniRios
force-pushed
the
06-26-new_paseo_binaries
branch
from
4fdc7af
to
d2196ca
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
The binaries for paseo were created with the politest runtime by accident. This was fixed already in a previous PR, but we needed to regenerate the binaries which will be force set on the Paseo network.
Why?
Made the runtime contain sudo pallet and the wrong runtime name