Use a pkginfo that supports 2.4 metadata

[twm]

Description

Require pkginfo>=1.12.0, which supports metadata 2.4. This allows Twine to work with packages generated by the latest hatchling. Refer to #678.

Also bump build-and-inspect-python-package to v2.11.0 for the same reason.

Checklist

• Make sure changes are covered by existing or new tests.
• For at least one Python version, make sure test pass on your local environment.
• Create a file in src/towncrier/newsfragments/. Briefly describe your
  changes, with information useful to end users. Your change will be included in the public release notes.
• Make sure all GitHub Actions checks are green (they are automatically checking all of the above).
• Ensure docs/tutorial.rst is still up-to-date.
• If you add new CLI arguments (or change the meaning of existing ones), make sure docs/cli.rst reflects those changes.
• If you add new configuration options (or change the meaning of existing ones), make sure docs/configuration.rst reflects those changes.

[glyph]

Yay?

[hynek]

You have to keep in mind that while the wheel is correct, Twine 6.0.1 will not upload licensing metadata (c.f. attrs's issue tracker & 329509342875 PRs around this). Since Towncrier has a license trove classifier, that might be mostly OK, but the metadata as it stands will not be uploaded until Twine ships a release with pypa/twine#1180

[adiroiban]

It look good. Thanks.

I guess that we need to trigger a new release to actually test this.

[adiroiban]

Maybe add this to the metadata.

If someone will try to run python -m build with an older pkginfo, I expect they will get an error.

Suggested change

	requires = ["hatchling"]
	requires = ["hatchling", "pkginfo>=1.12.0"]

[twm]

It actually builds fine without this — it is twine choking because of an old pkginfo.

[twm]

You have to keep in mind that while the wheel is correct, Twine 6.0.1 will not upload licensing metadata (c.f. attrs's issue tracker & 329509342875 PRs around this). Since Towncrier has a license trove classifier, that might be mostly OK, but the metadata as it stands will not be uploaded until Twine ships a release with pypa/twine#1180

That's interesting, thanks for the explanation. I don't think that doing a release without this metadata is a blocker, though, since no prior release has had it either.