-
-
Notifications
You must be signed in to change notification settings - Fork 688
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
Make a release 2.9.0? Or create a checklist that contributors can help with? #949
Comments
Also, we need a new release as 2.8.0 uses cryptography@41.0.7, which contains a vulnerability and is fixed in @42.0.0 https://security.snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6126975 @jpadilla, is there any ETA for the next release? |
@nghazali I just did a pip3 install pyjwt[crypto] and got PyJWT@2.8.0 and cryptography@42.0.5
|
@dsakagi something that would actually be super helpful would be compiling updates to CHANGELOG. |
Hi! Thanks for this project @jpadilla . It's great.
There are some changes that have already landed in
master
branch that I'm interested in having published as a new version that I could pull from PyPI.I'm willing to roll up my sleeves and pitch in if that would help the process along, but would need to have a few pointers on where to start (and where to finish!)
Expected Result
2.9.0 is released!
-or-
A checklist of tasks that contributors could help chip away at to help get 2.9.0 ready.
Actual Result
2.8.0 was the latest release last July. Additionally, it seems like builds on pushes to master have not been successful for some time. Is that part of what prevents making a 2.9 release?
Thanks again! Looking forward to hearing from you
The text was updated successfully, but these errors were encountered: