Configure metadata version manually #1872
Description
Background
Hatchling automatically determines metadata version when building a package. While hatchling==1.26.3 builds my package with Metadata-Version: 2.3 in the PKG-INFO, hatchling==1.27.0 builds it with Metadata-Version: 2.4. The PKG-INFO files seems identical in both cases except for the metadata version. It looks like it's impossible to configure the metadata version manually in pyproject.toml. This is an issue, because twine==6.0.1 is not supporting Metadata-Version: 2.4, but it is supporting Metadata-Version: 2.3 and lower.
Request
It would be great if there was an option to specify the metadata version manually in pyproject.toml file.
Another solution would be to always use minimal possible Metadata-Version.