-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make a release #151
Comments
Sadly we didn't have time to discuss this today in the meeting, I guess we can wait until next week. But just to clarify, do we expect this update to be a non-protocol update?
|
It can definitely wait until next week! We’re blocked on quite a lot of other things before being able to make a release anyway :) The questions you have are all good questions, and especially the wasmparser bump makes me think this should be a protocol update. In addition to that the next thing I’ll be working on is trying to integrate @nagisa’s work on finite-wasm into wasmer, which if landed before the next version can happen would very much definitely be a protocol update. (But then the good thing is it’d be so big that it’d deserve having a "wasmer3") Hence why I’ve been putting discussing what we want to do upon wasmer changes on the sync agenda for a few weeks, but didn’t push it more as we still have lots of time before being unblocked by other things anyway 😄 |
As per near/node-docs#55 (comment), this is currently blocked till the next nearcore release. |
This is currently being replaced by work in progress in near/nearcore#8323, vendoring wasmer into nearcore |
Closing as |
Bad bot! |
Go. AWAY! |
We should make a wasmer release.
This is currently blocked on:
Then we can make a release.
Once it’s done, we should be able to merge wasmer into the nearcore repository to simplify development
The text was updated successfully, but these errors were encountered: