-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Amend PRR #2474
Amend PRR #2474
Conversation
93f0bf1
to
c7d0e18
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for submitting the amendment, @AurevoirXavier, but please also remove the changes to other files in this PR.
Signed-off-by: Xavier Lau <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update. Sounds good, happy to support.
After conducting some research, I realized the node tools is currently ineffective. More and more teams decide to release their runtimes separately. For example, Polkadot, Acala, Moonbeam and..
But I also worked on other tasks. Initially, I thought it would be beneficial to use subwasm and subwasmlib, but I discovered that the crate is overly complex and bloated with unnecessary dependencies. Additionally, its version management is poorly maintained (e.g., this issue has persisted unresolved for over a year).
As a result, I decided to develop my own version, which provides a streamlined subset of subwasm‘s functionality. The goal isn’t to replace subwasm entirely but to enhance the release process. Specifically, it aims to replace subwasm within the release pipeline. My implementation natively interacts with Docker in Rust, offers improved error handling compared to shell-based approaches, and inspects essential information from WASM files. This makes it a much more practical tool for the release pipeline.
Also, this tool comes with a specific customized Docker image for Polkadot-SDK-based runtime build maintained by hack-ink.
Consequently, I updated the deliverables by replacing the node tools with this new solution.
Link #2373.