-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Release new major v5.0.0 #550
Comments
@Level/core I just released a premajor for |
I didn't realise we'd been so long since the last release, and wow there are lot of commits. If anyone else is interested here's the changelog so far (
|
@rvagg Hi! Nice to see you around! 👋 |
Also see the changelog and upgrade guide which summarize the above. |
@Level/core I released |
Hi @ralphtheninja - I'm on the n-api working group in Node. Congratulations on this release- very exciting to see an n-api version of leveldown get released- thank you for all your hard work on this! Is there a roadmap published somewhere that I can look at? I'm curious when 5.0 will become the default version in npm. |
@digitalinfinity No roadmap. We want to sort out cross compiled binaries first and it would be nice to get some testing done in related projects. I'm guessing we will release it soon ;) |
Great news! Thanks for the quick reply! |
@ralphtheninja is there any release date in sight? Soon Node.js v12 will be released and older leveldown versions do not work with Node.js v12. It would be great if this could be resolved quickly, so we get clean CITGM runs for before the official Node.js release. |
@BridgeAR There are some tasks that we'd like to complete before v5 but no musts. Which is to say, we can decide to release end of this week - or the week after that if it works out with the node.js schedule, giving us a little bit more time (we don't have a lot of capacity atm). |
The official release date is April 23. We'll have release candidates once a week starting from next week on and we'll have a lot of CITGM runs. It would therefore be great if the new version could be released as soon as possible. |
I hear you. I'll aim for friday (that's my open source day). Just can't make any promises. |
Done! |
Just making an issue for this for referencing other ongoing work. We will release some
rc
's first and once we have releasedv5.0.0
we should feed back into nodejs/node#25060The text was updated successfully, but these errors were encountered: