setuptools_scm >= 7 generates wheel version 0.0

[Nothing4You]

Hi,

I've been looking into updating aiomysql to setuptools_scm version 7.

In setuptools_scm < 7 both built sdist and wheel files are generated with the correct version in the file name:
https://github.com/Nothing4You/aiomysql/runs/7272226544?check_suite_focus=true#step:10:254

Attempting to update to setuptools_scm >= 7.0.4 produces a wheel file name using version 0.0:
Nothing4You/aiomysql@65e0caf
https://github.com/Nothing4You/aiomysql/runs/7272253138?check_suite_focus=true#step:10:258

For the generated sdist, the egg-info correctly includes Version: 0.1.2.dev19+g65e0caf and an appropriate generated scm version file.

For the generated wheel, the file is named aiomysql-0.0-py3-none-any.whl, egg-info contains Version: 0.0 and the generated version file says 0.0 as well.

I haven't been able to build a minimal reproducible example, as those have been generating the correct versions in my attempts.
I can reproduce it by taking the repo checked out at the commit linked above and running e.g. python -m build on it:

git clone -b scmtest https://github.com/Nothing4You/aiomysql/
cd aiomysql
python -m venv --upgrade-deps venv
. venv/bin/activate
pip install build
python -m build

Successfully built aiomysql-0.1.2.dev19+g65e0caf.tar.gz and aiomysql-0.0-py3-none-any.whl

[Nothing4You]

Individually generating only wheel or only sdist produces the correct version output.

[RonnyPfannschmidt]

@Nothing4You this seems to be a comeback of a git archival support regression,

[RonnyPfannschmidt]

the full isuse is that by going vcs -> sdist -> wheel, the issue triggers in the sdist, and a git archival is missparsed,
gonna try if i can create a quick bugfix

[Nothing4You]

thanks, appreciate the quick response.
i've been able to build a minimal reproduction example now, i forgot to actually commit relevant files before: https://github.com/Nothing4You/sscm-745

[Nothing4You]

thank you for the fix.

for my understanding, are the UserWarnings expected currently or is that a separate issue?

[RonnyPfannschmidt]

Warning is intended