-
Notifications
You must be signed in to change notification settings - Fork 549
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 3.x match 3.x-dev in case there is no stable release yet #501
Labels
feature request
New feature or request to improve the current logic
Comments
lazka
added
feature request
New feature or request to improve the current logic
needs triage
labels
Sep 20, 2022
lazka
changed the title
Make 3.X match dev versions in case there is no stable release yet
Make 3.x match 3.x-dev versions in case there is no stable release yet
Sep 20, 2022
lazka
changed the title
Make 3.x match 3.x-dev versions in case there is no stable release yet
Make 3.x match 3.x-dev in case there is no stable release yet
Sep 20, 2022
Yes, this would be a great feature. I support this! |
Hi @lazka, thank you for your help, we will take a look at this. |
This is #414 |
2 tasks
Let's consolidate on #213 since that's been around for a while and has more people following it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current situation: We will get 3.11 in about a month and I want to test it to CI from now on.
This means I now have to use
3.11-dev
and in one month downgrade to3.11
to get the stable release from then on.Ideally
3.11
would match3.11-dev
as long as there exists no stable release yet for that version, unless I'm missing something.I know it's possible to do
3.11.0-alpha - 3.11.0
but that still would require me to clean things up eventually and I'd like to add it once and never touch it again.The text was updated successfully, but these errors were encountered: