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.

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

add a note on upgrading to 3.0.1+ if running node 10 #471

Merged
merged 3 commits into from
May 15, 2018

Conversation

ralphtheninja
Copy link
Member

Closes #458

@vweevers
Copy link
Member

Didn't you say 2.0.2 and above work on node 10?

@ralphtheninja
Copy link
Member Author

@vweevers Technically, it compiles, but we don't have any prebuilt binaries for node 10 on those versions.

@ralphtheninja
Copy link
Member Author

Maybe we should clarify this as well.

UPGRADING.md Outdated
@@ -2,6 +2,10 @@

This document describes breaking changes and how to upgrade. For a complete list of changes including minor and patch releases, please refer to the [changelog](CHANGELOG.md).

## v3.0.1

If you're running node v10 or above you need to upgrade to `leveldown@2.0.1` or above. In addition, if you need prebuilt binaries you should upgrade to `leveldown@3.0.1` or above.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer "you'll need X" over "you need to X". And "or above" is implied, can be left out I think. But if you change it to "at least X to successfully compile" it becomes a subtle way to nudge people towards v3 :)

If you're running node v10 you'll need at least leveldown@2.0.1 to successfully compile from source. For prebuilt binaries please upgrade to leveldown@3.0.1.

@ralphtheninja ralphtheninja merged commit 9efc9b8 into master May 15, 2018
@ralphtheninja ralphtheninja deleted the upgrade-node-10 branch May 15, 2018 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants