Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configure metadata version manually #1872

Open
itymchyshyn-sc opened this issue Dec 30, 2024 · 0 comments
Open

Configure metadata version manually #1872

itymchyshyn-sc opened this issue Dec 30, 2024 · 0 comments

Comments

@itymchyshyn-sc
Copy link

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.
imagejan added a commit to fmi-faim/metamorph-mda-parser that referenced this issue Jan 3, 2025
@imagejan
Pin hatchling to 1.26.3
b931282 
See pypa/hatch#1872

(also remove unnecessary tool.hatch.metadata table)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@itymchyshyn-sc