3.1 release
#1511
Replies: 2 comments 4 replies
-
It is kinda close to the last release. Can't you use a GitHub commit reference for the requirements.txt for the time being? |
Beta Was this translation helpful? Give feedback.
1 reply
-
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>
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@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.
Beta Was this translation helpful? Give feedback.
All reactions