mcp
mcp copied to clipboard
Update repo to use net10.0
What does this PR do?
Replace the mixed net9.0, net10-preview dependency with the new net10.0 GA version.
Pre-merge Checklist
- [ ] Required for All PRs
- [ ] Read contribution guidelines
- [ ] PR title clearly describes the change
- [ ] Commit history is clean with descriptive messages (cleanup guide)
- [ ] Added comprehensive tests for new/modified functionality
- [ ] Updated
servers/Azure.Mcp.Server/CHANGELOG.mdand/orservers/Fabric.Mcp.Server/CHANGELOG.mdfor product changes (features, bug fixes, UI/UX, updated dependencies)
- [ ] For MCP tool changes:
- [ ] One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
- [ ] Updated
servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentation - [ ] Validate README.md changes using script at
eng/scripts/Process-PackageReadMe.ps1. See Package README - [ ] Updated command list in
/servers/Azure.Mcp.Server/docs/azmcp-commands.mdand/or/docs/fabric-commands.md - [ ] Run
.\eng\scripts\Update-AzCommandsMetadata.ps1to update tool metadata in azmcp-commands.md (required for CI) - [ ] For new or modified tool descriptions, ran
ToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test prompts - [ ] For tools with new names, including new tools or renamed tools, update
consolidated-tools.json - [ ] For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
- [ ] Extra steps for Azure MCP Server tool changes:
- [ ] Updated test prompts in
/servers/Azure.Mcp.Server/docs/e2eTestPrompts.md - [ ] 👉 For Community (non-Microsoft team member) PRs:
- [ ] Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (
crypto mining, spam, data exfiltration, etc.) - [ ] Manual tests run: added comment
/azp run mcp - pullrequest - liveto run Live Test Pipeline
- [ ] Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (
- [ ] Updated test prompts in