`hatch version` should be able to handle static version numbers

[warsaw]

I have a project that uses a static version number in its pyproject.toml file, e.g.

[project]
version = '0.9.0'

When I try to run hatch version minor on this project, I get an error message:

Cannot set version when it is statically defined by the `project.version` field

While I know it would mean changing the pyproject.toml file, I can't think of a reason why this shouldn't be possible. Is it a case of "not implemented yet" or is there a reason why you don't want to support hatch version [level] on a static version number?

I'm using hatch 1.9.4

[ofek]

I think it was a case of "if there is no dynamic update implementation from the configured plugin we don't know what to do" but as you mention we in fact know precisely what to do lol I can fix this

[trim21]

I can send a PR to support this

[trim21]

@ofek Do you mind review PR #1557 for this feature?

[fabiopicchi]

@ofek any reason why the PR was not accepted?

[ofek]

I didn't have time to review before the contributor closed it.

[fabiopicchi]

Oh wow. Ok! I'll try to work that out. Thanks for the swift response :)

[trim21]

fell free to cherry pick, I don't use hatch anymore so I don't want to wait for review

[fabiopicchi]

@ofek, here it is! I tried to simplify trim's code a bit, but couldn't do much better. I don't fully understand yet how hatch and hatchling depend on each other. Would need a deeper dive in the codebase to figure things out.

Please let me know if the PR looks good, and if not I would like to learn more about the project and get a deeper dive.