Closed mladendin closed 1 year ago
I can confirm that the same error happens in Bitbucket CI. Downgrading safety to v2.0.0 fixes the issue temporarily for me.
Looks like we were relying on the git
binary being present, which definitely isn't the case in all environments.
I've just merged in https://github.com/pyupio/safety/pull/397 which has a fix for this, and a new dot release will be up soon!
Safety 2.1.1 is out and published with this fix!
Thank you for the quick reaction, guys.
Description
It seems like there is an issue with the new release. This is how my Gitlab CI looks like which prior to the latest version(2.1.) was working just fine.
For some reason, I'm getting this error message now: