Draft
Conversation
The shim package and its release workflow served the 0.1.x transition from pydantic-harness to pydantic-ai-harness. With this merged, the next pydantic-ai-harness release is free to be 0.2.0 without needing to maintain the shim. MERGE ONLY AFTER: - pydantic-harness==0.1.1 has been published to PyPI - All users are expected to have migrated, or are willing to pin the old 0.1.x line MERGE BEFORE: - Tagging pydantic-ai-harness v0.2.0 (since the shim pins pydantic-ai-harness<0.2 and there's no point keeping it around once the upper bound kicks in) Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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
Removes the
pydantic-harnesscompatibility shim that was added in #208 to bridge the rename frompydantic-harnesstopydantic-ai-harness.Removed
legacy/pydantic-harness/— the shim package (pyproject.toml,pydantic_harness/__init__.py,code_mode/__init__.py, README).github/workflows/release-shim.yml— the one-off publish workflowlegacyexclusions from ruff and pyright config inpyproject.tomlTiming
Draft until ready to merge. This PR should only land:
pydantic-harness==0.1.1has been published to PyPI (so users have somewhere to land for the 0.1.x line)pydantic-ai-harness v0.2.0(since the shim pinspydantic-ai-harness<0.2and there's no point keeping it around once the upper bound kicks in — the rejected resolution will force migration anyway)Between those two moments, new users installing
pydantic-harnessstill get the shim → the new package → a DeprecationWarning telling them to migrate. After merging this PR, new installs ofpydantic-harnesswill continue to resolve to the published 0.1.1 shim on PyPI (unaffected by repo cleanup), but no further shim releases are possible.Test plan
make lintpassesmake typecheckpassesmake testpassespydantic-harness==0.1.1is on PyPI before merge🤖 Generated with Claude Code