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

bump PyYAML to 5.1 for CVE-2017-18342 #69

Merged
merged 2 commits into from Mar 22, 2019
Merged

Conversation

dtkav
Copy link
Contributor

@dtkav dtkav commented Mar 15, 2019

PyYAML 5.1 was released a few days ago. Hopefully this alleviates the concerns that were raised with using the beta release (4.1b).

I've reverted the security note that was added as well, as it no longer applies.

Backwards incompatible changes are listed here : yaml/pyyaml#265

@codecov
Copy link

codecov bot commented Mar 15, 2019

Codecov Report

Merging #69 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #69   +/-   ##
=======================================
  Coverage   98.57%   98.57%           
=======================================
  Files          13       13           
  Lines         421      421           
=======================================
  Hits          415      415           
  Misses          6        6

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 74d26ab...f21bd0e. Read the comment docs.

@dtkav dtkav changed the title WIP: bump PyYAML to 5.1 for CVE-2017-18342 bump PyYAML to 5.1 for CVE-2017-18342 Mar 15, 2019
This reverts commit dcd0c2a.
@p1c2u p1c2u merged commit 7fef38a into python-openapi:master Mar 22, 2019
@MRigal
Copy link

MRigal commented May 2, 2019

@p1c2u What about releasing a new version containing this security patch?

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

3 participants