-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Dependent Package "packaging" upgrade halts invocation #4011
Comments
yes I am experience the exact same problem started few hours ago |
Wee workaround for now, run it in docker if you can @YustinS For ADO:
|
Thanks for that. I instead just explicitly installed the working version of
|
Thank you all for reporting @YustinS @tyconsulting @philthynz et al. We pinned the version of packaging for now, will work on a more permanent solution (see #4013 ) Fixed version is checkov 2.2.125 |
thanks, i've tested my ADO pipeline. It's working again |
Describe the issue
Currently we are running checkov in a CI environment in Azure DevOps over our Terraform configurations. Earlier today Checkov started failing to run, at first it was believed to link to the release that occurred earlier.
Investigation though has shown that the dependency
packaging
has also had a release, wherein it has droppedLegacyVersion
from its codebase (see stack trace).The quick solution is to pin
packaging==21.3
to ensure the needed codebase functionality is in place.This seems to only apply to environments that fresh install everything, as this was innoticed in local development until the CI pipeline triggered the issue.
Examples
In the ADO CI this simple version should recreate the behavior:
Exception Trace
Desktop (please complete the following information):
Additional context
Release in packaging that causes this issue is
22.0
,21.3
appears to function as expected.The text was updated successfully, but these errors were encountered: