Update bcrypt to the latest version 🚀 #316
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
|
greenkeeper[bot] seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Version 2.0.1 just got published. |
Version 3.0.0 just got published. |
Update to this version instead 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
|
Update to this version instead 🚀 Release Notes for v3.0.3
CommitsThe new version differs by 8 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v3.0.4
|
Update to this version instead 🚀 Release Notes for v3.0.5bcrypt 3.0.5 CommitsThe new version differs by 6 commits.
See the full diff |
|
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.0.0 of bcrypt was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of bcrypt.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 26 commits.
ab026b2v2.0.0f00d4b8Merge pull request #589 from agathver/libc-awaredab435einstall and use any-promise (#504)9a9ab45Make binaries libc awareaac593cMerge pull request #587 from agathver/hash-version-support2d45be1Allow to choose bcrypt minor version0ea1b36Merge pull request #549 from agathver/2b-hashes4c44f20Add support for $2b$ hashese8cde51Merge pull request #583 from ofrobots/async-resource6a79eaffix: propagate async context88590eaMerge pull request #584 from kelektiv/snyk-fix-bc6682901da0f44fix: package.json to reduce vulnerabilities43734e3Merge pull request #564 from david-a-wheeler/readme-timingf2bec20README: comparisons resist timing attacks096a34fMerge pull request #554 from agathver/node-9There are 26 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴