KeyError: 'scm_version' when scm_version is None in dump_version

[tauroid]

I think due to the default .py version template now containing an unconditional reference to scm_version, scm_version being None and write_to being a Python file will always cause a KeyError. It seems like the commit ID should default to None, but I don't know this codebase well enough to say for sure. C.f. #1154

[mwiarda]

We used hatch-vcs but didn't freeze the version of setuptools-scm in our product versions.
Now this issue broke our build for all existing versions 😢

[pafi-code]

Yea this bug kind of kills every install of packages that use setuptools-scm or like in our case hatch-vcs. The only fix would be to limit the setuptools-scm version in the pyproject.toml of each project, which feels unfeasible.

[mwiarda]

Adding this line in your pyproject.toml is a workaround:

[tool.hatch.build.hooks.vcs]
template = "__version__ = '{version}'"

But all previous versions are still broken.

[pafi-code]

@mwiarda Yea that's not really a fix. The fix would be what @tauroid is suggesting I strongly assume.

[RonnyPfannschmidt]

Bugfix is in progress

[RonnyPfannschmidt]

version 9.0 was yanked as a second regression was found and we dont want to leave things broken until i fix both