.NET: Re-enable AzureAI.Persistent packaging and integration tests#4865
Merged
rogerbarreto merged 1 commit intoMar 24, 2026
Merged
Conversation
…icrosoft#4769) Azure.AI.Agents.Persistent 1.2.0-beta.10 now targets ME.AI 10.4.0+, resolving the compatibility issue that required disabling this package. - Remove IsPackable=false from the csproj - Re-enable all 6 integration test classes (IntegrationDisabled → Integration) - Remove outdated compatibility warning from README.md Co-authored-by: Copilot <[email protected]>
markwallace-microsoft
added
documentation
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
Pull request overview
Re-enables packaging and CI integration testing for the Microsoft.Agents.AI.AzureAI.Persistent .NET integration layer now that Azure.AI.Agents.Persistent has updated compatibility with Microsoft.Extensions.AI 10.4.0+.
Changes:
- Re-enabled NuGet packaging for
Microsoft.Agents.AI.AzureAI.Persistentby removing theIsPackable=falseoverride. - Re-enabled Azure AI Persistent integration test classes by switching their test category trait back to
"Integration". - Removed the now-obsolete compatibility warning block from the package README.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| dotnet/src/Microsoft.Agents.AI.AzureAI.Persistent/Microsoft.Agents.AI.AzureAI.Persistent.csproj | Allows the project to be packable again for NuGet shipping. |
| dotnet/src/Microsoft.Agents.AI.AzureAI.Persistent/README.md | Removes outdated compatibility limitation content. |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentCreateTests.cs | Re-enables integration test class via trait change. |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentRunTests.cs | Re-enables integration test class via trait change. |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentRunStreamingTests.cs | Re-enables integration test class via trait change. |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentStructuredOutputRunTests.cs | Re-enables integration test class via trait change (but current logic still skips tests). |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsChatClientAgentRunTests.cs | Re-enables integration test class via trait change. |
| dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsChatClientAgentRunStreamingTests.cs | Re-enables integration test class via trait change. |
Comments suppressed due to low confidence (1)
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentStructuredOutputRunTests.cs:12
SkipReasonis a non-null const string, soAssert.SkipWhen(SkipReason is not null, ...)will always evaluate true and these structured-output integration tests will always be skipped even after re-enabling the[Trait("Category", "Integration")]category. If these tests are meant to run again, make the skip conditional (e.g., based on an env var/CI detection) or remove the overrides and let the base tests execute; if they must stay disabled, consider marking them with an explicit xUnit Skip attribute or reverting this class back to an IntegrationDisabled category to avoid giving a false sense of coverage.
[Trait("Category", "Integration")]
public class AzureAIAgentsPersistentStructuredOutputRunTests() : StructuredOutputRunTests<AzureAIAgentsPersistentFixture>(() => new())
{
private const string SkipReason = "Fails intermittently on the build agent/CI";
SergeyMenshykh
approved these changes
Mar 24, 2026
westey-m
approved these changes
Mar 24, 2026
Merged
This was referenced Apr 3, 2026
This was referenced May 5, 2026
Closed
This was referenced May 12, 2026
This was referenced May 19, 2026
This was referenced May 29, 2026
This was referenced Jun 6, 2026
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
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.
Motivation and Context
Azure.AI.Agents.Persistent1.2.0-beta.10 now targetsMicrosoft.Extensions.AI10.4.0+, resolving the compatibility issue (McpServerToolApprovalResponseContent→ToolApprovalResponseContentrename) that required disabling this package from NuGet shipping and its integration tests.Closes #4769
Description
<IsPackable>false</IsPackable>fromMicrosoft.Agents.AI.AzureAI.Persistent.csprojto re-enable NuGet packaging[Trait("Category", "IntegrationDisabled")]→[Trait("Category", "Integration")]and removing the associated disable commentsREADME.mdContribution Checklist