Skip to content
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 version #17

Merged
merged 4 commits into from
May 13, 2020
Merged

Update pyyaml version #17

merged 4 commits into from
May 13, 2020

Conversation

Sticky-Bits
Copy link
Contributor

Vulnerability in pyyaml version we were using. Updated to latest and confirmed tests pass.

https://nvd.nist.gov/vuln/detail/CVE-2017-18342

@jarekwg
Copy link
Member

jarekwg commented Sep 4, 2019

The github warning also points out the version in pipfile.lock. Could do both at the same time?

@Sticky-Bits
Copy link
Contributor Author

Dependency mismatch - docker-compose requires pyyaml < 4.x.

We're not actually affected by the vulnerability, so we can just merge this later.
I'll push up the Pipfile with the required version, and when the compose guys update thier pyyaml version we can merge.

Watch this space: docker/compose#6619

@jarekwg
Copy link
Member

jarekwg commented Apr 16, 2020

Looks like docker-compose has been updated now.

@jarekwg jarekwg changed the base branch from master to develop May 13, 2020 01:17
@jarekwg jarekwg merged commit d365e69 into develop May 13, 2020
@jarekwg jarekwg deleted the feature/pyyaml-upgrade branch May 13, 2020 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants