build: pin hatchling to exclude broken 1.32.1 - #733
Merged
Merged
Conversation
hatchling 1.32.1 (PyPI, 2026-09-16 16:52 UTC) adds `from hatch.plugin.manager import PluginManager` to hatchling/builders/binary.py, but hatchling does not depend on hatch. Every isolated build env that resolves the unpinned `hatchling` requirement now fails at import time with `ModuleNotFoundError: No module named 'hatch'`, so the `build` CI matrix is red on every PR opened since that release (main was green at 22:40 UTC the day before). Pin `build-system.requires` in all seven packages to `hatchling!=1.32.1,<1.33`: exclude the known-broken release, let the upstream patch release through, and keep the next minor from landing untested. Verified locally: `hatch build` in the insight and conformance-tests-otel packages fails before this change and succeeds after it, resolving hatchling 1.32.0.
Contributor
Codex AI reviewNo actionable findings. Residual risk: isolated distribution builds were not executed during this read-only review; CI’s Python 3.11–3.14 build matrix should validate resolution and packaging. Reviewed commit |
yaythomas
approved these changes
Sep 16, 2026
This branch was successfully deployed
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
2 participants
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.
Summary
CI's
build (3.11–3.14)matrix is red on every PR opened since this morning. The "Build distribution" step dies before touching any package source:Cause:
hatchling1.32.1 was published to PyPI at 16:52 UTC today. It addsfrom hatch.plugin.manager import PluginManagertohatchling/builders/binary.py(the import is not present in 1.32.0), buthatchlingdoes not declare a dependency onhatch, so every isolated build environment that resolves our unpinnedrequires = ["hatchling"]now fails at import. Every CI run before 16:52 UTC is green, includingmainat 22:40 UTC yesterday; every run since 17:08 UTC is red across three unrelated branches (#732 and two feature branches).Fix: pin
build-system.requiresin all seven packages tohatchling!=1.32.1,<1.33.!=1.32.1excludes the known-broken release and lets the upstream patch release through without another PR.<1.33keeps the next minor from landing in CI untested. Bump it deliberately.Only
[build-system].requireschanges;build-backend, package metadata, and runtime dependencies are untouched.Testing
Locally, in
packages/aws-durable-execution-sdk-python-insightandpackages/aws-durable-execution-sdk-python-conformance-tests-otel:hatch buildfails with theModuleNotFoundErrorabove (the isolated env had resolved 1.32.1).hatch buildsucceeds for both, producing the sdist and wheel; the isolated env resolvedhatchling1.32.0.CI on this PR is the real check: the
buildmatrix must go green with no other change.Unblocks #732.