AI & .NET

dotnet/extensions releases v10.8.1 is now available

The dotnet/extensions repository published v10.8.1 on 2026-07-21. The release notes list changes including: Fix FICC tool_calls/tool ordering with approvals and service-managed chat history #7617 by @westey-m; Roundtrip OpenAI Responses reasoning item id for stateless (store=false) encrypted reasoning #7629 by @rogerbarreto (co-authored by @tarekgh).

What was released From the source

dotnet/extensions published v10.8.1 on GitHub on 2026-07-21. Items listed in the release notes include:

  • Fix FICC tool_calls/tool ordering with approvals and service-managed chat history #7617 by @westey-m
  • Roundtrip OpenAI Responses reasoning item id for stateless (store=false) encrypted reasoning #7629 by @rogerbarreto (co-authored by @tarekgh)
  • @jozkee reviewed pull requests

At a glance · AI & .NET

Stable release10.8.1

What was releasedWhy it mattersWho should careUpgrade considerations

Why it matters Analysis

AI libraries for .NET evolve quickly, and APIs in preview often change between releases. Following updates helps teams choose stable abstractions and avoid building on APIs that are about to change.

Who should care Analysis

  • .NET developers building AI-enabled features
  • Teams evaluating model providers and orchestration libraries
  • Architects defining AI integration patterns

Upgrade considerations Analysis

  1. Read the complete release notes for breaking changes and known issues.
  2. Update the relevant NuGet packages in a branch and run your tests before merging.
  3. Read the linked release notes for breaking changes between versions.
  4. Review data-handling and cost implications of any model provider you connect to.

Sources and further reading

Original: “dotnet/extensions releases v10.8.1”, dotnet/extensions releases (Microsoft.Extensions.AI and more), published 21 Jul 2026, retrieved 16 Oct 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.