chore(deps-dev): bump types-docker from 7.1.0.20260518 to 7.2.0.20260728 - #1090
Merged
Merged
Conversation
Bumps [types-docker](https://github.com/python/typeshed) from 7.1.0.20260518 to 7.2.0.20260728. - [Commits](https://github.com/python/typeshed/commits) --- updated-dependencies: - dependency-name: types-docker dependency-version: 7.2.0.20260728 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Aug 15, 2026
Tranquility2
added a commit
that referenced
this pull request
Aug 15, 2026
Fixes #1096 ## Problem The `Run twine check` CI step fails on all PRs (e.g. run [31887608422](https://github.com/testcontainers/testcontainers-python/actions/runs/31887608422/job/95019090461?pr=1090) on #1090) with: ``` Checking dist/testcontainers-4.15.0-py3-none-any.whl: ERROR InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version ``` ## Root cause `hatchling>=1.32` started emitting `Metadata-Version: 2.5` in built wheel/sdist metadata. The pinned `twine` (6.2.0, via `packaging`) doesn't yet recognize `2.5` as valid and rejects the distribution. This is unrelated to any specific PR's diff — it's an unpinned build-backend version issue. See pypa/twine#1327. ## Fix Pin `hatchling` to `>=1.26,<1.32` in `pyproject.toml`'s `[build-system]` so it keeps emitting `Metadata-Version: 2.4`, compatible with the current twine/packaging toolchain. ## Verification Ran locally: ``` uv build && uv run twine check dist/* ``` Wheel METADATA now shows `Metadata-Version: 2.4`, and both wheel and sdist pass `twine check` (`PASSED`). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6536a34d-6afa-4f02-81ed-89dc72586d04
Tranquility2
approved these changes
Aug 15, 2026
alexanderankin
pushed a commit
that referenced
this pull request
Aug 16, 2026
…1100) ## Problem The `Run twine check` CI step fails on all PRs (e.g. run [31887608422](https://github.com/testcontainers/testcontainers-python/actions/runs/31887608422/job/95019090461?pr=1090) on #1090) with: ``` Checking dist/testcontainers-4.15.0-py3-none-any.whl: ERROR InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version ``` Root cause and original tracking issue: #1096. ## Fix `hatchling` emits `Metadata-Version: 2.5` in built wheel/sdist metadata. Rather than pinning `hatchling` back to an older version (as done in #1095), this upgrades `twine` to `>=7.0.0`, which officially added support for Metadata-Version 2.5, fixing the root cause instead of working around it. Supersedes #1095 as the preferred fix. ## Verification Ran locally: ``` uv build && uv run twine check dist/* ``` Wheel METADATA shows `Metadata-Version: 2.5` (hatchling unpinned), and both wheel and sdist pass `twine check` (`PASSED`).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps types-docker from 7.1.0.20260518 to 7.2.0.20260728.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)