-
Notifications
You must be signed in to change notification settings - Fork 32
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
Update ramda dependency #110
Conversation
@adepretis @fhelmberger @busypeoples @AutoSponge sorry for the inconvenience, not sure if you are still maintaining this repo, but it would be really nice if this can be merged. Thanks a lot in advance! |
Just merged it. Unfortunately this project is no longer maintained @crash7 :-( @busypeoples do you want to officially take over the repository? Otherwise would you be interested @crash7? |
Thanks @adepretis! Do you know if a new release will be triggered? |
@icavina uh, good point. As far as I remember we never had a pipeline in place and the package was published without organizational scope - so I guess @busypeoples has been maintaining this on npm. Can you publish it once again/once more? |
@adepretis thanks for merging this! Happy to help with future PRs reviews or security updates! |
@adepretis I can also handle the npm publish if you want or if @busypeoples is not available. |
I don't have the credentials @crash7 ... trying to get a hold of @busypeoples currently, I'll get back to you ASAP |
@crash7 Thanks for the PR! Will publish an update. Thanks for merging @adepretis. |
Ok, published |
Thank you @busypeoples! |
I need to solve a couple of security issues that older ramda versions have. Check all the usage and it's safe to update to latest.