-
Hi. I'm trying to tag my develop releases but I don't want How can I do this? [tool.bumpversion]
commit = true
commit_args = "--no-verify"
current_version = "0.6.2.dev1"
message = "BumpVersion: updated from {current_version} to {new_version}"
parse = "(?P<major>\\d+)\\.(?P<minor>\\d+)\\.(?P<patch>\\d+)(\\.(?P<dev>dev\\d+))?"
serialize = [
"{major}.{minor}.{patch}.{dev}{distance_to_latest_tag}",
"{major}.{minor}.{patch}",
]
tag = true
[tool.bumpversion.parts.dev]
values = ["release", "dev"] |
Beta Was this translation helpful? Give feedback.
Answered by
coordt
Sep 4, 2023
Replies: 1 comment 1 reply
-
@coordt Sorry to bump this up, could you help me regarding this matter? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There isn't a way to differentiate between different types of tags.
I have been using a workflow where I bump and release the version, but do not commit or tag the changes. This saves on extra commits on the feature branch and accomplishes the result: dev releases.
I have this process automated in GitHub actions. The basic logic is "if you aren't on the primary branch, do a dev release."
Also, I'm sorry about the late response. I don't get notified when people create issues or discussions. I have to go looking for them, and sometimes miss them.