Repository navigation
Cap pydantic-ai-skills below 2 for the Common AI skills extra - #74899
Merged
Merged
Conversation
pydantic-ai-skills 2.0 removed SkillsToolset, which AgentSkillsToolset wraps, and the skills extra had no upper bound, so a fresh install resolved 2.1.0 and every AgentSkillsToolset run failed with an error telling the user to install the extra they already had. Cap the extra and the dev group at >=1.2.0,<2, and make the error name the installed version and the supported range when pydantic-ai-skills is present but has no SkillsToolset. Drop the root exclude-newer cutoff that kept uv.lock on 1.2.0, so CI now tests 1.4.0, the latest 1.x.
potiuk
approved these changes
Oct 17, 2026
1 task done
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Oct 17, 2026
common.ai 1.0.0 was pulled from the 2026-10-14 wave so it could ship with the pydantic-ai-skills cap (apache#74899): its "skills" extra allowed pydantic-ai-skills 2.x, which breaks a fresh install at run time. 1.0.0 was never published, so rc2 keeps the version and the changelog section grows with everything that has merged since rc1. openai's common.compat floor was still the "use next version" placeholder from apache#74149, which admits common.compat releases that lack get_async_extra_dejson; 1.21.0 is the first one that has it. Generated-by: Claude Opus 5
potiuk
added a commit
that referenced
this pull request
Oct 17, 2026
common.ai 1.0.0 was pulled from the 2026-10-14 wave so it could ship with the pydantic-ai-skills cap (#74899): its "skills" extra allowed pydantic-ai-skills 2.x, which breaks a fresh install at run time. 1.0.0 was never published, so rc2 keeps the version and the changelog section grows with everything that has merged since rc1. openai's common.compat floor was still the "use next version" placeholder from #74149, which admits common.compat releases that lack get_async_extra_dejson; 1.21.0 is the first one that has it. Generated-by: Claude Opus 5
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.
AgentSkillsToolsetfails on every run in a fresh install of the Common AI provider with theskillsextra. The extra asks forpydantic-ai-skills>=1.2.0with no upper bound, so today it resolves 2.1.0 (checked withuv pip compileagainst the released 0.10.0). pydantic-ai-skills 2.0 removedSkillsToolset, which the toolset wraps, so the import in__aenter__fails before the first model request. The error then tells the user to install theskillsextra, which they already have.This caps the extra and the dev dependency group at
>=1.2.0,<2. 1.2.0, 1.3.0 and 1.4.0 all exportSkillsToolset; 2.0.0 and 2.1.0 do not. The error now separates the two cases: ifpydantic_ai_skillsis missing, it still points at the extra; if it is installed withoutSkillsToolset, it names the installed version and the supported range.Why CI didn't catch it. The root
pyproject.tomlhad a temporaryexclude-newer-packagecutoff for pydantic-ai-skills (in both blocks), added so 1.2.0 could resolve inside the exclude-newer window. It keptuv.lockon 1.2.0, so no later release was ever tested. With the cap in place the cutoff is no longer needed, so this removes it, and the lock now moves to 1.4.0, the latest 1.x. That is the only package that changes inuv.lock. The existingAgentSkillsToolsettests pass on 1.4.0.Why a cap rather than a port to 2.x. 2.0 is a rewrite, not a rename: it removes
SkillsToolset, leavingSkillsCapability(which 1.x already ships), so each skill loads as a deferred pydantic-ai capability, and the tool names the model sees change. Supporting it means movingAgentSkillsToolsetontocapabilities=and remappingexclude_tools/exclude_resources. That belongs in its own PR, and the cap fixes installs now.Users on an affected release can pin
pydantic-ai-skills<2next toapache-airflow-providers-common-ai[skills].Related to #74741