Require Twine 7 for metadata 2.5 uploads

[nubtron]

What does this PR do?

Raises the minimum Twine version in datadog_checks_dev[cli] from 1.11.0 to 7.0.0.

Twine 7 supports uploading distributions that use core metadata 2.5. The associated changelog fragment will be consumed by a separate datadog_checks_dev 40.0.1 release PR after this PR merges.

Motivation

The datadog_checks_dev-40.0.0 workflow built a valid metadata-2.5 wheel but failed before upload because the publisher's older Twine rejected that metadata version. PR #24847 updated the GitHub publishing action to v1.14.2, which includes Twine 7.

datadog_checks_dev also provides the manual ddev release upload fallback, which invokes Twine directly. Requiring Twine 7 ensures that fallback can upload the same metadata-2.5 artifacts.

References:

• Twine 7.0.0 changelog
• Twine documentation
• Python core metadata specification
• Failed 40.0.0 publication

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: RUN-ALL — every test task will run
Trigger:         empty diff (default branch, scheduled run, or shallow-clone fallback)
Test tasks:      0 (all selected)
Publish tasks:   1 (always emitted)
Diff:            empty (no diff information)

Learn more about CI impact filtering

[datadog-prod-us1-4]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 88.86%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 06306c0 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run