Python: Clarify Foundry 1.12 Projects <2.4 bound and supported Projects 2.6 upgrade path

[arush-saxena]

Description

Could the maintainers clarify the supported upgrade path from azure-ai-projects 2.3 to 2.4+ / 2.6 when using the current stable agent-framework-foundry 1.12.0?

Published metadata currently declares:

Distribution	Relevant requirement
agent-framework-foundry==1.12.0	azure-ai-projects>=2.2.0,<2.4.0
agent-framework-openai==1.14.2	openai>=2.25.0,<4
azure-ai-projects==2.6.0	openai>=3.0.0

The OpenAI-major overlap now exists with adapter 1.14.2, but Foundry's independent Projects upper bound still prevents combining the two latest stable Foundry/Projects distributions. This is a dependency-resolution/support question, not a claim that a specific stable Projects API is broken.

Release-history context

• Python: Clean up dependency groups and compatibility #7046 capped Projects below 2.3, citing an incompatible 2.3 API change.
• Python: Consolidate dependency updates #7204 added support for stable hosted-session/toolbox namespaces with preview fallbacks and moved the upper bound to <2.4.0.
• Python: allow OpenAI SDK 3.x #7967 added OpenAI 3.x support, including transport-neutral handling and CI lanes.

The <2.4 bound was introduced before Projects 2.4 was published. I could not find an explicit explanation for retaining it through Foundry 1.12.0.

Questions

1. Does <2.4 reflect a demonstrated Projects 2.4+ incompatibility, a deliberately validated/support window, or metadata awaiting an update?
2. If there is a known incompatibility, which APIs/behaviors and tracking issue or regression tests describe it?
3. Now that the OpenAI adapter supports SDK 3.x, what work remains for Foundry to support Projects 2.6?
4. Which coherent stable package set do maintainers recommend for applications that need Projects 2.4+ features without overriding dependency constraints or reverting functionality?

Minimal dependency conflict

These requirements cannot be resolved together under the published metadata:

agent-framework-foundry==1.12.0
azure-ai-projects==2.6.0

The conflict is azure-ai-projects<2.4.0 versus azure-ai-projects==2.6.0.
No dependency override, --no-deps installation, or live service call is needed to establish that conflict.

Package versions and sources

• Core: 1.17.0
• Foundry: 1.12.0
• OpenAI adapter: 1.14.2
• Projects: 2.6.0
• Python: 3.13
• Foundry metadata
• OpenAI adapter metadata
• Projects metadata

We are retaining a locked baseline while investigating candidate upgrades. An older Foundry release's broader bound is not being treated as evidence of support for newer Projects behavior.

[arush-saxena]

Additional bounded evidence: normal uv0.12.7 resolution rejects Foundry1.12.0 + Projects2.6.0 exactly because Projects>=2.2,<2.4 conflicts with==2.6.0. Separately, Python3.13.15 can resolve/install Core1.17.0 + olderFoundry1.10.1 + OpenAIadapter1.14.2 + Projects2.6.0 + OpenAI3.8.0 (HTTPX2 2.12.0), with uv pip check passing. Projects/Foundry client constructors and the safe Harness factory/local session construct offline; this does not exercise remote session creation, Responses, MCP or Azure authentication. We are not treating the older adapter range as support evidence or overriding1.12 bounds. The specific clarification remains: what known behavior or validation/support boundary keeps the current Foundry package capped below2.4, and what is the maintainer-recommended forward path? No production upgrade was made.