Release 3.1.1

[JonathanHuot]

Based on latest contributions and the previous release was not so recent, I suggest to release 3.1.1.

That will be a good opportunity for @auvipy to make your first release, if you want ;)

BTW: to synchronize that will be helpful if you join the oauthlib gitter community.

[auvipy]

what is the link? I would love to contribute to the release 👯‍♂️

[auvipy]

i joined!

[JonathanHuot]

I tried to add milestone "3.1.1" to closed issues and PR. Then, it could be useful to create a PR with Changelog description, and maybe we could discuss based on that.

Once everything are in master, tagging the new version should trigger the build process to release a github version and pypi. I think we should probably document the release process as well.

[auvipy]

that sounds reasonable to me

[mvaled]

What's the status of this release?

[JonathanHuot]

@mvaled : it is ready, only some paperwork are still needed to deploy it.
@auvipy : do you have time to finish it for this year?

[auvipy]

I can, but do I need PyPI access for that?

[JonathanHuot]

The release rollout must be done by creating a PR with all changelog and version changes. Once it is reviewed and merged, we can tag the git revision and tagging will automatically release a pypi release with Travis.

[auvipy]

The release rollout must be done by creating a PR with all changelog and version changes. Once it is reviewed and merged, we can tag the git revision and tagging will automatically release a pypi release with Travis.

oh OK

[valentijnscholten]

I think this is really needed because with the newer pips installing requirements may break due to the dependency on an old PyJWT version: b69fa53

[Sri-krishna98]

Yes oauthlib 3.1.0 is already causing CVE issues checkout PRISMA-2021-0041, the CVE scan setup in our pipeline throws a high severity vulnerability for this package, can you please update it as it's been quite some time

[rolweber]

Hmm, this issue was created a year ago, and still no new release. Things seem to have stalled a bit.

That CVE 2021-0041 is currently reserved, but not yet disclosed. Maybe a fix is in the making.

[JonathanHuot]

Give me a couple of days and I will trigger the release. Thanks for your patience

[Sri-krishna98]

Thanks for looking into this👍

…

On Wed, May 12, 2021, 3:21 PM Jonathan Huot ***@***.***> wrote: Give me a couple of days and I will trigger the release. Thanks for your patience — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#736 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKYROFT6TPX5IPRNXTNPGIDTNJFRHANCNFSM4M62ML7Q> .

[JonathanHuot]

Release is finally out. Sorry for the delay, and enjoy...
3.2.0 coming soon with remaining PRs

[ankit-jha]

Release is finally out. Sorry for the delay, and enjoy... 3.2.0 coming soon with remaining PRs

Please start the new year with the new release.
We're waiting on it.