potiuk opened a new pull request, #74935:
URL: https://github.com/apache/airflow/pull/74935

   A copy of #74904 by Kaxil Naik (his two commits, authorship kept) with fixes 
for the two provider metadata tests it broke, so it can go through review and 
into common.ai 1.0.0rc3.
   
   From #74904: the supported-services rows for sandboxes, managed agents and 
DataFusion now match what the provider ships; the changelog's `get_schema` note 
says `result.get("truncated")`; the Anthropic, Strands and ADK guides name the 
`sql` extra their examples need; and a new guide, **Writing your own toolset** 
(`toolsets/custom.rst`), comes with an example Dag that calls PyPI through 
`HttpHook`.
   
   On top of that:
   - The `SandboxToolset` row no longer links `sandbox/backends` inline. 
`test_toolset_table_entries_match_supported_services_rst` allows one `:doc:` 
target per toolset row, and the row already links `sandbox/index`.
   - `System One servers` is left out of the `pydanticai` connection's vendor 
list. `system-one:` only exists from pydantic-ai 2.53.0, while `uv.lock` has 
2.48.0 and every declared vendor must exist from 2.45.0 
(`test_no_declared_vendor_is_absent_upstream`). `decision_models.rst` still 
documents the prefix.
   - The example's `version` pattern must start with a letter or digit, like 
`name`, so `.` or `..` can no longer change the PyPI path the hook calls, as 
the guide says.
   - A 1.0.0 changelog entry, so the change ships in rc3.
   
   `test_provider_metadata.py`: 15 passed locally.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to