Configuration to get the next version based on current git branch

[splashcd]

[tool.versioningit.vcs]
method = "git"
match = ["build-{branch}-v*"]

[tool.versioningit.tag2version]
rmprefix = "build-{branch}-v"

[tool.versioningit.next-version]
method = "smallest-release"

[tool.versioningit.format]
distance = "{next_version}"
dirty = "{next_version}"
distance-dirty = "{next_version}"

I would like versioningit to determine the git branch I'm currently on, and return the next version based on that branch's latest tag.

However, this doesn't seem to be working for me.

> git branch --show-current
my-feature-branch-name

> git tag -l "*my-feature-branch-name*"
build-my-feature-branch-name-v1.0.0.110
build-my-feature-branch-name-v1.1.0.0

> uvx versioningit -n
versioningit: NoTagError: `git describe --long --dirty --always --tags '--match=build-{branch}-v*'` could not find a tag

This works as expected when I replace {branch} with the actual branch name. Where am I going wrong?

uv: 0.7.7
versioningit: 3.1.3
Python: 3.9.2
os: Debian GNU/Linux 11

[jwodder]

The vcs.match field does not support placeholders like {branch}, and likewise for tag2version.rmprefix.

[bsturgeon-vs]

@jwodder is there some other way to support @splashcd's root ask? If a branch is made from main-1.0.1, but then main is bumped to main-1.0.4, the feature branch will also report its version as 1.0.4 despite based on 1.0.1. What configuration of versioningit supports that kind of historical consistency?

[jwodder]

is there some other way to support @splashcd's root ask?

With the current versioningit, not unless someone writes a plugin that provides a VCS method that acts like git but supports placeholders in match. Theoretically, I could add support for this to versioningit, but it seems like a niche use-case.

If a branch is made from main-1.0.1, but then main is bumped to main-1.0.4, the feature branch will also report its version as 1.0.4 despite based on 1.0.1.

That doesn't sound right. versioningit gets the latest tag using git describe, so if you're building on a branch that is not descended from a 1.0.4 tag, the captured version won't be 1.0.4. In scenarios where you've seen this, were you merging or rebasing main back into the feature branch after the 1.0.4 tag?

[bsturgeon-vs]

Ah. Yes, thanks for making me recheck. When I tested my feature branch was at 1.0.0.4 while main was 1.0.0.5 so I panicked when feature branch reported 1.0.0.5, but it was reporting next version. The same command on main reports 1.0.0.6.

Thanks for your time.