Skip to content
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.

Sign up for GitHub

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 note for FeatureManagement 3.1.0 #839

Merged
merged 9 commits into from
Nov 30, 2023
Merged

Add release note for FeatureManagement 3.1.0 #839

Changes from 5 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
9d2d682
Update FeatureManagement 3.1.0 release note
zhiyuanliang-ms Nov 23, 2023
835036d
update
zhiyuanliang-ms Nov 24, 2023
62ac7d9
update
zhiyuanliang-ms Nov 28, 2023
4af54a6
Resolve comments
zhiyuanliang-ms Nov 28, 2023
67a9989
Update
zhiyuanliang-ms Nov 29, 2023
dd927ae
Re-added issue references
zhiyuanliang-ms Nov 30, 2023
68e78be
Rewrite the Blazor support section
zhiyuanliang-ms Nov 30, 2023
90b49ba
Add issue reference
zhiyuanliang-ms Nov 30, 2023
5b58549
Add indentation
zhiyuanliang-ms Nov 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions releaseNotes/Microsoft.Featuremanagement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,30 @@
# Microsoft.FeatureManagement.AspNetCore
[Source code ][source_code_web] | [Package (NuGet)][package_web] | [Samples][samples_web] | [Product documentation][docs]

## 3.1.0 - November 23, 2023

### Enhancements

* `FeatureManager` and `ConfigurationFeatureDefinitionProvider` are now public.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought there was an issue we can reference. Do we have one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

* Enables usage of external dependency injection containers.
* Allows usage of `FeatureManager` without requiring dependency injection.

* Added [Blazor](https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor) support for [additional security scenarios](https://learn.microsoft.com/en-us/aspnet/core/blazor/security/server/additional-scenarios?view=aspnetcore-7.0#pass-tokens-to-a-server-side-blazor-app).
* Added `AddScopedFeatureManagement()` method to register the feature manager and feature filters as scoped by default.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should combine above, and tell customers what's the difference of the new API and where to use it. Suggest below:

Added support for server-side Blazor apps, where the following API can be used in place of the existing AddFeatureManagement() API. The new API registers the feature manager and feature filters as scoped services, while the existing API registers them as singletons.

// full signature of the API

Is there a issue we can reference?

* Allows usage of scoped feature filters with context provider services to mitigate the [security risk](https://learn.microsoft.com/en-us/aspnet/core/blazor/security/server/interactive-server-side-rendering?view=aspnetcore-7.0#ihttpcontextaccessorhttpcontext-in-razor-components) when using `HttpContextAccessor` in Blazor components.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is part of the blazor support. We should drop it.


### Bug Fixes
* Fixed a bug introduced in the previous release where feature flags cannot be loaded from a custom section of configuration.
* Fixed a bug introduced in the previous release where evaluation of a feature flag that references a contextual feature filter may throw an exception if there is no appropriate context provided during evaluation.
zhiyuanliang-ms marked this conversation as resolved.
Show resolved Hide resolved

## 3.0.0 - October 27, 2023

### Breaking Changes

* Dropped netcoreapp3.1 and net5.0 target frameworks since both have reached the end of their life cycle. https://github.com/microsoft/FeatureManagement-Dotnet/pull/267
* All feature flags must be defined in a `FeatureManagement` section within configuration. Previously flags were discovered at the top level of configuration if the `FeatureManagement` section was not defined, but this functionality has been removed. https://github.com/microsoft/FeatureManagement-Dotnet/pull/261

### Changes
### Enhancements

* Built-in filters are registered by default. https://github.com/microsoft/FeatureManagement-Dotnet/pull/287
This includes:
Expand All @@ -23,7 +39,7 @@
* Added netstandard 2.1 as a target framework in the Microsoft.FeatureManagement package. https://github.com/microsoft/FeatureManagement-Dotnet/pull/267
* Added net7.0 as a target framework in the Microsoft.FeatureManagement.AspNetCore package. https://github.com/microsoft/FeatureManagement-Dotnet/pull/267

## Bug Fixes
### Bug Fixes
* Prevents the usage of colon in Feature names.
* Adjusts log level for noisy warning when feature definitions are not found.
* Fixed an edge case in targeting if a user is allocated to exactly the 100th percentile (~1 in 2 billion chance)
Expand Down