We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Because of recent semver-major changes that couldn't make it to Node 10, almost every new change to crypto code now has conflicts.
Here is the list of commits that need to be backported:
/cc @nodejs/crypto
The text was updated successfully, but these errors were encountered:
@targos Consider me in on the effort. We could begin by making a checklist of sorts.
Sorry, something went wrong.
I will try to backport my changes as soon as possible, I have been a bit busy the last few weeks, sorry.
I'll take a look at mine next week.
Thank you all. Note that the list is in the order of the commits on master. It will probably be easier to do the backports in the same order.
I opened #20706, please take a look.
No branches or pull requests
Because of recent semver-major changes that couldn't make it to Node 10, almost every new change to crypto code now has conflicts.
Here is the list of commits that need to be backported:
/cc @nodejs/crypto
The text was updated successfully, but these errors were encountered: