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
Plans to cut stable release? #259
Comments
There is an active project board for the 5.1 release: https://github.com/yaml/pyyaml/projects/2 I've been keeping an eye on it as I'm also very interested in seeing 5.1 released as soon as possible. |
Can we please have a new RELEASE asap (not pre-release) that covers the CVE issue? There are lots of projects which have a policy of not listing pre-releases in their requirements. |
We are working on it, but there were several issues that prevented us from doing a final release. |
I got a security alert on github about a vulnerability on the current stable release 3.13. They recommend to update to version >=4.1b1. I would suggest to make one of the latest releases as |
According to #193 (comment) there should be a release in the next few days. |
We are hoping to have a final release in the next 3 days. |
FYI... PyYAML 5.1 appears to be ready to ship in the next 24 hours. |
PyYAML 5.1 has been released. |
requirements.io has been yelling at this project I've been helping maintain, https://github.com/jlaska/pytest-github because we have
pyYAML
in our requirements file, but this gets 3.13 from pypi because the subsequent releases have been marked aspre-releases
https://pypi.org/project/PyYAML/#history
Do you have plans to cut another stable release?
The text was updated successfully, but these errors were encountered: