Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add "next" #521

Open
maelle opened this issue Sep 5, 2022 · 1 comment · Fixed by #524
Open

Add "next" #521

maelle opened this issue Sep 5, 2022 · 1 comment · Fixed by #524
Assignees
@maelle

Comments

@maelle
Copy link
Member

maelle commented Sep 5, 2022

Via @krlmlr's comment

I just realized we might want another option: "next", moving from pre-minor to minor and from pre-major to major, and to patch otherwise. Would be the default option to pre_release() .

in #412

I'd tackle this issue... next 😸
@maelle maelle added this to the 0.1.1 milestone Sep 5, 2022
@maelle maelle self-assigned this Sep 5, 2022
@maelle maelle mentioned this issue Sep 5, 2022
Merged
@maelle
Copy link
Member Author

maelle commented Sep 6, 2022

#524 (comment)

@maelle maelle reopened this Sep 6, 2022
@krlmlr krlmlr removed this from the 0.1.1 milestone Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maelle maelle

Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: New default pre_release(which = "next") cynkra/fledge
2 participants
@krlmlr @maelle