3.1 release

[dopry]

@n2ygk How do you feel about me cutting a 3.1 release? I'd like to get the wildcard feature out there, partly because I need it.

[n2ygk]

It is kinda close to the last release. Can't you use a GitHub commit reference for the requirements.txt for the time being?

[dopry]

I can and am... I just don't see much reason to hold up a release. other people may want it... I'm pretty used to semantic-release deploying every merge on my other projects

[n2ygk]

Well since you are volunteering to do it, sure!

…

On Wed, Oct 2, 2024 at 2:05 PM dopry ***@***.***> wrote: I can and am... I just don't see much reason to hold up a release. other people may want it... I'm pretty used to semantic-release deploying every merge on my other projects — Reply to this email directly, view it on GitHub <#1511 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBHS5YIJLHWJ6FRXBR2D53ZZQYVTAVCNFSM6AAAAABPIDM7D6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBSGM4TMOI> . You are receiving this because you were mentioned.Message ID: <jazzband/django-oauth-toolkit/repo-discussions/1511/comments/10823969@ github.com>

[dopry]

doesn't look like I'm getting to it this week. got caught up with the logout confirmation screen issue. so maybe next week. :)

[n2ygk]

@dopry are you able to do this? I noticed that the Jazzband request to make you a lead has not happened yet...

[dopry]

I can probably pick this back up now. Waiting on pypi access still.

[n2ygk]

You have pypi access now.

[dopry]

Yep got it... Need to update the release.yml to publish... can you check out #1592, it has the release workflow updates...