-
Notifications
You must be signed in to change notification settings - Fork 12
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 PyYAML to 5.4.1 #219
Comments
to avoid having to monitor yet another slack channel, we could add a nightly to the repos to show safety failures in github |
Initially suggested by @creviera in freedomofpress/securedrop-builder#219 (comment), let's add a nightly CI run to show CI failures in GitHub.
Great idea. I've added a commit for both client and proxy to add nightly CI runs in freedomofpress/securedrop-client#1222 and freedomofpress/securedrop-proxy#82 respectively. (SDK already has nightly builds, see https://github.com/freedomofpress/securedrop-sdk/blob/15bc20af8113148db173add854c7844fad65078e/.circleci/config.yml#L82-L91) |
CI is currently failing in proxy, client and sdk repositories due to CVE-2020-14343. associated to the version of PyYAML used:
It looks like in the case of Client and SDK, PyYAML is only a dev dependency: only the proxy uses PyYAML in a production context.
@kushaldas has already done a diff review in https://github.com/freedomofpress/securedrop-debian-packaging/wiki/PyYAML-5.3.1-to-5.4.1
The text was updated successfully, but these errors were encountered: