microsoft-foundry / microsoft-foundry/foundry-samples
Bug: pip resolution failure in hosted agent samples — agent-framework meta-package pins conflicting agent-framework-core versions
@herohua is already working on this.
Since Jul 28, 2026.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 494
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 38
Description
Bug
Affected: 13 of 16 hosted agent response samples (samples/python/hosted-agents/agent-framework/responses/)
Impact: Hosted Agent quickstart is broken, blocking Tracing + Evaluate quickstarts downstream.
Root cause
requirements.txt in most samples uses:
agent-framework>=1.2.2
agent-framework-foundry-hosting
When pip resolves agent-framework to 1.2.2, it pins agent-framework-core==1.2.2. But agent-framework-orchestrations 1.0.0 (a transitive dep) requires agent-framework-core>=1.9.0. Pip cannot satisfy both:
ERROR: Cannot install agent-framework-core and agent-framework-core[all]==1.2.2
agent-framework 1.2.2 depends on agent-framework-core==1.2.2
agent-framework-orchestrations 1.0.0 depends on agent-framework-core>=1.9.0
ERROR: ResolutionImpossible
Samples already fixed (working pattern)
Samples 11-azure-search-rag, 12-foundry-skills, and 13-foundry-memory already work around this by using agent-framework-foundry (narrow subpackage) instead of the agent-framework meta-package.
Proposed fix
Replace agent-framework / agent-framework[foundry]>=1.2.2 with agent-framework-foundry in all 13 affected samples. Also add mcp>=1.24.0 where missing (runtime dep not declared by agent-framework-core).
A complete branch with the fix is available at: https://github.com/VBhadauria/foundry-samples/tree/fix/requirements-dep-conflict
Draft PR (auto-closed by bot): https://github.com/microsoft-foundry/foundry-samples/pull/783
Affected samples
| Sample | Current requirements | Status |
|---|---|---|
| 01-basic | agent-framework>=1.2.2 |
❌ broken |
| 02-tools | agent-framework>=1.2.2 |
❌ broken |
| 03-mcp | agent-framework>=1.2.2 |
❌ broken |
| 04-foundry-toolbox | agent-framework[foundry]>=1.2.2 |
❌ broken |
| 05-workflows | agent-framework>=1.2.2 |
❌ broken |
| 06-files | agent-framework (bare) |
❌ broken |
| 07-skills | agent-framework>=1.2.2 |
❌ broken |
| 07-teams-activity | agent-framework[foundry]>=1.2.2 |
❌ broken |
| 08-observability | agent-framework (bare) |
❌ broken |
| 09-declarative-customer-support | agent-framework (bare) |
❌ broken |
| 10-downstream-azure | agent-framework>=1.2.2 |
❌ broken |
| 15-optimization-travel-approver | agent-framework>=1.2.2 |
❌ broken |
| 16-content-safety-guardrail | agent-framework>=1.2.2 |
❌ broken |
Verification
Tested all 13 samples with pip install --dry-run (Python 3.13):
- Before (
agent-framework==1.2.2): ❌ResolutionImpossiblefor all 13 - After (
agent-framework-foundry): ✅ Resolves cleanly for all 13
cc @AniketSinha-Microsoft
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.