Bumping date with another segment does not produce expected result

[wallacms]

In my pyproject.toml I have:

[build-system]
requires = ["hatchling", "hatch-calver"]
build-backend = "hatchling.build"

[tool.hatch.version]
path = "my_package/__init__.py"
scheme = "calver"
calver-scheme = 'YY.0M'

if the current version that hatch version reports is 25.05.1 and I run hatch version date,patch I would expect it to bump the version to 25.05.2. Instead it reports:

ValueError: Version `25.05.1` is not higher than the original version `25.05.1`

Running hatch version patch in this case does the right thing, but if the current version is 25.04.1 and the current date is May 21, 2025, then hatch version patch bumps the version to 25.04.2

I'd like to be able to run hatch version date,patch and have it always set the date according to the calver-scheme and then always increment the patch version

[akx]

I see where you're coming from.

date resets the patch level to zero, so hatch version date,patch,patch would get you to 25.05.2.

Maybe a new syntax, like hatch version date,+patch would be the ticket here, iow, +patch would capture the patch version before the other directives were applied, and increment it and splat it in place?

[wallacms]

It's possible that I'm using CalVer in a way that's not intended, but I'm basically just looking for a version that I can always increment that contains some notion of the date. I'm trying to use this in a CI context where I can just bump the version after every commit that passes CI.

So the behavior I'd like is:

• 25.05.1 -> 25.05.2 (if the current month is still May)
• 25.05.5 -> 25.06.1 (if the current month is now June)

I think this is slightly different than what you proposed above, where +patch would result in 25.06.6 in the second example.