fix: replace agent-framework meta-package with agent-framework-foundry to resolve pip conflicts#783
Closed
VBhadauria wants to merge 1 commit into
Closed
Conversation
…y in requirements.txt The agent-framework meta-package pins agent-framework-core==1.2.2, but agent-framework-orchestrations 1.0.0 (a transitive dependency) requires agent-framework-core>=1.9.0. This makes pip unable to resolve dependencies, breaking the hosted agent quickstart and downstream samples (tracing, evaluate). Replace agent-framework (and agent-framework[foundry]) with the narrow agent-framework-foundry subpackage in all affected samples, following the pattern already used successfully by samples 11, 12, and 13. Also add mcp>=1.24.0 as an explicit dependency where missing, since it is needed at runtime but not declared by agent-framework-core. Affected samples: 01-basic, 02-tools, 03-mcp, 04-foundry-toolbox, 05-workflows, 06-files, 07-skills, 07-teams-activity, 08-observability, 09-declarative-customer-support, 10-downstream-azure, 15-optimization-travel-approver, 16-content-safety-guardrail. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
👋 Thanks for your interest in contributing, @VBhadauria! This repository does not accept pull requests directly. If you'd like to report a bug, suggest an improvement, or propose a new sample, please open an issue instead. If you are a Microsoft-internal contributor, please submit your PR through foundry-samples-pr instead. See CONTRIBUTING.md for more details. |
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.
Problem
agent-framework>=1.2.2inrequirements.txtcan resolve to version 1.2.2, which pinsagent-framework-core==1.2.2. However,agent-framework-orchestrations 1.0.0(a transitive dependency) requiresagent-framework-core>=1.9.0. This makes pip unable to resolve dependencies, breaking the hosted agent quickstart and all downstream samples (Tracing, Evaluate).Fix
Replace
agent-framework/agent-framework[foundry]>=1.2.2with the narrowagent-framework-foundrysubpackage in all affected samples. This follows the pattern already used successfully by samples 11-azure-search-rag, 12-foundry-skills, and 13-foundry-memory.Also adds
mcp>=1.24.0as an explicit dependency where missing, since it is needed at runtime but not declared byagent-framework-core.Affected samples (13 total)
01-basic(Hosted Agent quickstart)02-tools03-mcp04-foundry-toolbox05-workflows06-files07-skills07-teams-activity08-observability09-declarative-customer-support10-downstream-azure15-optimization-travel-approver16-content-safety-guardrailVerification
Tested all 13 samples with
pip install --dry-runusing Python 3.13:agent-framework==1.2.2)ResolutionImpossiblefor all 13agent-framework-foundry)cc @AniketSinha-Microsoft