-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add release notes for .NET provider 7.0.0 #838
Changes from 3 commits
39d0beb
82a90f9
c93891f
a9d2ed5
d74d2f5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,24 @@ | ||
## Microsoft.Extensions.Configuration.AzureAppConfiguration | ||
### [Package (NuGet)](https://www.nuget.org/packages/Microsoft.Extensions.Configuration.AzureAppConfiguration) | ||
|
||
### 7.0.0 - November 21, 2023 | ||
### Breaking Changes | ||
* Removed .NET Core 3.1 as a target framework as .NET Core 3.1 is out of support. Updated `Microsoft.Extensions` dependencies to version 6.0.0 and later. [#482](https://github.com/Azure/AppConfiguration-DotnetProvider/pull/482) | ||
* `AddAzureAppConfiguration` now throws errors for invalid inputs when the `optional` flag is equal to `true`. [#408](https://github.com/Azure/AppConfiguration-DotnetProvider/pull/408) | ||
amerjusupovic marked this conversation as resolved.
Show resolved
Hide resolved
amerjusupovic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
### Enhancements | ||
* This is the first stable release of the following API introduced in the 7.0.0-preview release. [#422](https://github.com/Azure/AppConfiguration-DotnetProvider/pull/422) | ||
amerjusupovic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
```cs | ||
public AzureAppConfigurationOptions SelectSnapshot(string name) | ||
``` | ||
* Added support for the `requirement_type` property for feature flags introduced in version 2.6.0-preview of the Microsoft.FeatureManagement library. [#475](https://github.com/Azure/AppConfiguration-DotnetProvider/pull/475) | ||
amerjusupovic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
* The provider will now continuously retry when loading data from App Configuration on startup until either the load is successful or the timeout value in `AzureAppConfigurationOptions.StartupOptions.Timeout` has elapsed. `AzureAppConfigurationOptions.StartupOptions` can be set using the following new API. [#488](https://github.com/Azure/AppConfiguration-DotnetProvider/pull/488) | ||
amerjusupovic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
```cs | ||
public AzureAppConfigurationOptions ConfigureStartupOptions(Action<StartupOptions> configure) | ||
``` | ||
|
||
### 7.0.0-preview.2 - August 24, 2023 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was released before 6.1.1. Can we change the order? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wasn't sure if it's clear that 6.1.1 will not contain changes from 7.0.0-preview2, but if it is then should be ok. |
||
* Includes all changes made in `6.1.0`. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dropping netcoreapp3.1 is a breaking change for
Microsoft.Azure.AppConfiguration.AspNetCore
, not for this package.What are those
Microsoft.Extensions.*
changes really for?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the package versions don't really need to be mentioned. I can move this to the AspNetCore file and should I mention the inclusion of .netstandard2.1 as a target here instead?