chore(deps): complete hatchling 1.31.0 bump (both pin locations)#13
Merged
Conversation
Dependabot PR #12 only bumped the build-system pin in the root pyproject.toml, but CI installs hatchling from .github/requirements-ci.lock (via requirements-ci.in), leaving 1.27.0 installed and failing `python -m build --no-isolation` with an unmet-dependency error. tools/vlabs-prm-eval/pyproject.toml carries the same build-system pin and is built with --no-build-isolation too. Bump hatchling to 1.31.0 in all four locations (root pyproject.toml, tools/vlabs-prm-eval/pyproject.toml, requirements-ci.in, requirements-ci.lock with official PyPI sha256 hashes). Dependency set is unchanged between 1.27.0 and 1.31.0, so no other lock entries need to move. Verified locally on Python 3.12: hash-locked install, editable prm-eval install, and `python -m build --no-isolation` for both packages all succeed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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
Dependabot PR #12 bumps hatchling 1.27.0 → 1.31.0 in the root
pyproject.toml[build-system] requires, but CI installs hatchling from a separate pin —.github/requirements-ci.lock(generated from.github/requirements-ci.in) viapip install --require-hashes. With only the pyproject side bumped,python -m build --no-isolationfails with:This PR completes the bump in all pin locations:
pyproject.toml—requires = ["hatchling==1.31.0"]tools/vlabs-prm-eval/pyproject.toml— same build-system pin (also built with--no-build-isolationin CI).github/requirements-ci.in—hatchling==1.31.0.github/requirements-ci.lock— hatchling entry updated with the official PyPI sha256 hashes (wheel + sdist)hatchling's dependency set is unchanged between 1.27.0 and 1.31.0 (
packaging>=24.2,pathspec>=0.10.1,pluggy>=1.0.0,trove-classifiers;tomlionly for <3.11), so no other lock entries need to move.Verification
Locally recreated the CI environment on Python 3.12:
pip install --require-hashes -r .github/requirements-ci.lock, editable--no-deps --no-build-isolationinstall oftools/vlabs-prm-eval, thenpython -m build --no-isolationfor both the root package and vlabs-prm-eval — all succeed.Supersedes #12.
🤖 Generated with Claude Code