-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Polly dependency to latest release? #31705
Comments
@martincostello thanks for contacting us. Are there known breaking changes between 7.2.2 and 7.1.0? I think we would be open to a PR if there are no breaking changes, otherwise we would need to evaluate the impact. |
Thanks for contacting us. |
@javiercn No, there shouldn't be any breaking changes. There's no changes to the public API other than the addition of the new If you'd be happy to accept a PR to update the dependency then I'll open one later on today 👍 |
@martincostello go for it. |
Update Polly dependency to the latest version of the package. Addresses dotnet#31705.
Done via #31708 |
Is your feature request related to a problem? Please describe.
ASP.NET Core currently depends on Polly 7.1.0, which was released in March 2019.
aspnetcore/eng/Versions.props
Line 249 in 1870441
Since then there have been a number of minor releases, the most recent being yesterday to 7.2.2, to fix a number of bugs and minor improvements (CHANGELOG).
Describe the solution you'd like
Update the Polly dependency to the latest release, 7.2.2.
Updating to at least 7.2.0 would also make the new
IConcurrentPolicyRegistry
interface available, which could then be registered by default in the Polly extensions for HttpClientFactory: #28283 (comment).Assuming there isn't a specific reason to pin the dependency at 7.1.0, I'd be happy to raise a PR to update the minimum version for ASP.NET Core 6.0.
The text was updated successfully, but these errors were encountered: