Upgrade Jimp to address minimist security vulnerability #4
Conversation
Co-Authored-By: Corbin Crutchley <crutchcorn@gmail.com>
|
@karlhorky with the goal of being more proactive about merging PRs and publishing them, I added CI via GitHub actions, which required a package-lock.json file. Can you fix your branch so this is present and the checks pass? Otherwise it doesn't seem that the Jimp releases have changed anything we care about so I think we should be good. Thanks. |
|
Ah, I wasn't aware that your fork is the official repository now! Do you have contact with @iwasawafag? Maybe his repo can be transferred to you instead of maintaining a fork (or placed under an organization), to minimize future confusion... Alternately, at the very least probably a very large "Deprecated" warning with a link to your fork should be at the top of the readme... I have opened this new pull request instead, which has been also linked from the old one: #5 |
Clone of iwsfg#11