Drafted with assistance of GitHub Copilot
Polly will adopt the Open Source Maintenance Fee for maintained binary releases beginning November 16, 2026.
This directly affects the .NET resilience packages:
Microsoft.Extensions.Resilience explicitly references Polly packages.
This alone requires Microsoft to take an OSMF license.Microsoft.Extensions.Resilience and Microsoft.Extensions.Http.Resilience expose Polly types through stable public APIs, including ResilienceContext, ResiliencePipeline<T>, Outcome<T>, and Polly strategy option classes.
Although Polly is transitive in the package graph, that source-level use may be considered direct for our users. The current OSMF guidance indicates that is not the case via its examples re: using statements, but it is not airtight.
Could the maintainers clarify:
- Whether these packages will continue using official Polly binaries after November 16, with Microsoft licensing Polly.
- Whether Microsoft is considering temporarily freezing the Polly version, building it from source, maintaining or adopting a fork, replacing it, or redesigning the affected APIs.
- Whether consumers using exposed Polly types remain (or not) covered by the transitive-dependency exemption or be covered (or not) by custom Microsoft licensing.
A freeze may be a reasonable temporary measure, but it needs a servicing policy and an exit plan. Community forks such as Fences are beginning to appear, but none is yet an established replacement.
Polly will adopt the Open Source Maintenance Fee for maintained binary releases beginning November 16, 2026.
This directly affects the .NET resilience packages:
Microsoft.Extensions.Resilienceexplicitly references Polly packages.This alone requires Microsoft to take an OSMF license.
Microsoft.Extensions.ResilienceandMicrosoft.Extensions.Http.Resilienceexpose Polly types through stable public APIs, includingResilienceContext,ResiliencePipeline<T>,Outcome<T>, and Polly strategy option classes.Although Polly is transitive in the package graph, that source-level use may be considered direct for our users. The current OSMF guidance indicates that is not the case via its examples re:
usingstatements, but it is not airtight.Could the maintainers clarify:
A freeze may be a reasonable temporary measure, but it needs a servicing policy and an exit plan. Community forks such as Fences are beginning to appear, but none is yet an established replacement.