Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stabilize the wasm-node public API #264

Closed
tomaka opened this issue Mar 3, 2023 · 2 comments · Fixed by #282
Closed

Stabilize the wasm-node public API #264

tomaka opened this issue Mar 3, 2023 · 2 comments · Fixed by #282

Comments

@tomaka
Copy link
Contributor

tomaka commented Mar 3, 2023

Do a clean-up pass on the public API of the wasm-node, in order to later publish v1.0.
@tomaka
Copy link
Contributor Author

tomaka commented Mar 11, 2023

Note that this implicitly means stabilizing the chain spec format as well. If you pass a chain spec to smoldot v1.0, then update smoldot to v1.1, the same chain spec should continue to parse.
This isn't great due to paritytech/polkadot-sdk#60, but we'll just ignore that problem and do a smooth transition if it ever gets fixed.

@tomaka
Copy link
Contributor Author

tomaka commented Mar 11, 2023

Also paritytech/substrate#91 would require breaking changes, but that's probably not coming any time soon.

This was referenced Mar 11, 2023
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Publish v1.0.0 tomaka/smoldot
1 participant
@tomaka