Skip to content

Bump Microsoft.FeatureManagement.AspNetCore from 3.2.0 to 4.3.0 #115

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

Jump to bottom
Closed
dependabot wants to merge 1 commit into from
Closed

Bump Microsoft.FeatureManagement.AspNetCore from 3.2.0 to 4.3.0 #115

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 8, 2025

Updated Microsoft.FeatureManagement.AspNetCore from 3.2.0 to 4.3.0.

Release notes

Sourced from Microsoft.FeatureManagement.AspNetCore's releases.

4.3.0

4.3.0 - August 27, 2025

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Introduced ConfigurationFeatureDefinitionProviderOptions which allows to enable the new configuration merging behavior for the built-in ConfiguationFeatureDefinitionProvider. When the same feature flag is defined in multiple sources, definitions are merged according to configuration provider registration order, with the last feature flag definition taking precedence in case of conflicts. #​552

Microsoft.FeatureManagement.AspNetCore

Enhancements

  • Updated Microsoft.FeatureManagement reference to 4.3.0. See the release notes for more information on the changes.

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

Enhancements

  • Updated Microsoft.FeatureManagement reference to 4.3.0. See the release notes for more information on the changes.

4.1.0

4.1.0 - May 22, 2025

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Added DefaultWhenEnabled and VariantAssignmentPercentage fields to the FeatureEvaluation event. #​495

Microsoft.FeatureManagement.AspNetCore

Enhancements

  • Updated Microsoft.FeatureManagement reference to 4.1.0. See the release notes for more information on the changes.

Bug Fix

  • Fixed a bug that caused duplicated dimension in Application Insights telemetry. #​542

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

Enhancements

  • Updated Microsoft.FeatureManagement reference to 4.1.0. See the release notes for more information on the changes.

Bug Fix

  • Fixed a bug that caused duplicated dimension in Application Insights telemetry. #​542

4.0.0

4.0.0 - November 1, 2024

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

Variant Feature Flags

A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).

The new IVariantFeatureManager has been introduced as the successor to the existing IFeatureManager. It retains all the functionalities of IFeatureManager while adding new GetVariantAsync methods and supporting CancellationToken for all methods.

IVariantFeatureManager featureManager;
...
Variant variant = await featureManager.GetVariantAsync(MyFeatureFlags.HelpText, CancellationToken.None);
model.Text = variant.Configuration.Value;

Note: If reading variant flags from App Configuration, version 8.0.0 or above for the Microsoft.Extensions.Configuration.AzureAppConfiguration or Microsoft.Azure.AppConfiguration.AspNetCore package is required.

For more details on Variants, see here.

Variant Service Provider

Variant feature flags can be used in conjunction with dependency injection to surface different implementations of a service for different users. This is accomplished by using the Variant Service Provider.

For more details on Variant Service Provider, see here

Telemetry

Telemetry provides observability into flag evaluations, offering insights into which users received specific flag results. This enables more powerful metric analysis, such as experimentation.

For more details on Telemetry, see here.

Microsoft Feature Management Schema

Added support for variant feature flags defined using Microsoft Feature Management schema. Variants and telemetry can be declared using Microsoft Feature Flag schema v2. Here is a Sample.

Performance Optimizations

The performance of the feature flag state evaluation has been improved by up to 20%, with a memory reduction of up to 30% for .NET 8 applications compared to the version 3.5.0 release.
... (truncated)

4.0.0-preview5

4.0.0-preview5 - Oct 24, 2024

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Added support for injecting additional telemetry fields on feature evaluation events if telemetry is enabled.
    • DefaultWhenEnabled reflects what the DefaultWhenEnabled variant on the flag is.
    • VariantAssignmentPercentage shows what percentage of users will be allocated the given Variant for the given Reason.

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview5.

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview5.

4.0.0-preview4

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • The feature flag telemetry pipeline is now integrated with .NET Acitivity instrumentation. Feature manager now has an AcitvitySource called "Microsoft.FeatureManagement". If telemetry is enabled for a feature flag, whenever the feature flag is evaluated, feature manager will start an Activity and add an ActivityEvent with tags containing feature evaluation information. #​455

Breaking Changes

  • If you were using earlier preview versions of this package and configuration files to define variant feature flags, they are no longer supported in the .NET Feature Management schema. Instead, please use the Microsoft Feature Management schema to define variant feature flags. #​421.

  • AddTelemetryPublisher API and ITelemetryPublisher interface were removed. The feature flag telemetry pipeline is now integrated with .NET Acitivity instrumentation. #​455

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview4.

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview4.

Enhancements

  • Introduced a new API AddApplicationInsightsTelemetryPublisher to register a feature flag telemetry publisher for Application Insights. #​455

    builder.Services.AddFeatureManagement()
                .WithTargeting()
                .AddApplicationInsightsTelemetryPublisher();

Breaking Changes

  • The TargetingTelemetryInitializer type has been moved to this package from the now-deprecated Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore package. This change simplifies the utilization of feature flag telemetry.

  • The type ApplicationInsightsTelemetryPublisher has been removed as its functionality has been replaced with the new API AddApplicationInsightsTelemetryPublisher for publishing feature flag telemetry to Application Insights. #​455

4.0.0-preview3

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Added support for variant feature flags defined using Microsoft Feature Management schema. Variants and telemetry can be declared using Microsoft Feature Flag schema v2. The Microsoft Feature Management schema is designed to be language agnostic, enabling you to apply a consistent feature management configuration across Microsoft feature management libraries of different programming languages.

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview3.

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

Breaking Changes

  • Updated the namespace for ApplicationInsightsTelemetryPublisher to Microsoft.FeatureManagement.Telemetry. In the future, developers using any of our offered telemetry publishers will no longer need to specify the service specific namespaces like using Microsoft.FeatureManagement.Telemetry.ApplicationInsights.

  • Updated the namespace for TrackEvent extension method of TelemetryClient to Microsoft.ApplicationInsights. The previous directive using Microsoft.FeatureManagement.Telemetry.ApplicationInsights is no longer required when calling the TrackEvent method.

Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 4.0.0-preview3.

4.0.0-preview2

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Added support for variant feature flag-based service provider in dependency injection. It allows different service implementations to be injected automatically for different targeted audiences based on their variant assignment. (#​39). See more details here.
  • Added a TargetingContext property to the EvaluationEvent. This allows feature evaluation events to accurately represent what the targeting context was at the time of feature evaluation. (#​409)

Microsoft.FeatureManagement.AspNetCore

Enhancements

  • Introduced a new ASP.NET Core middleware called TargetingHttpContextMiddleware. It makes targeting information available from HttpContext on each request. (#​409)
  • Added support for .NET 8 target framework. (#​364)

Microsoft.FeatureManagement.Telemetry.ApplicationInsights

Enhancements

  • Added a TargetingId property to the feature evaluation events sent to Application Insights. The TargetingId is the identifier of a targeted user during feature evaluation. This new property allows you to correlate feature evaluation events with other telemetry data your application sends to Application Insights, as long as they share the same TargetingId. (#​409)

Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore

Enhancements

  • Introduced a telemetry initializer named TargetingTelemetryInitializer. It automatically adds targeting information to telemetry data your application sends to Application Insights. This can be used to correlate your telemetry data with feature evaluation events based on the targeting information during your telemetry analysis. (#​409)

4.0.0-preview

Microsoft.FeatureManagement Updates

The packages associated with this release are

Variants

Variants are a tool that can be used to surface different variations of a feature to different segments of an audience. Previously, this library only worked with flags. The flags were limited to boolean values, as they are either enabled or disabled. Variants have dynamic values. They can be string, int, a complex object, or a reference to a ConfigurationSection.

//
// Modify view based off multiple possible variants
Variant variant = await featureManager.GetVariantAsync(MyFeatureFlags.BackgroundUrl);

model.BackgroundUrl = variant.Configuration.Value;

return View(model);

Variants are defined within a Feature, under a new section named "Variants". Variants are assigned by allocation, defined in a new section named "Allocation".

"BackgroundUrl": {
    "Variants": [
        {
            "Name": "GetStarted",
            "ConfigurationValue": "https://learn.microsoft.com/en-us/media/illustrations/biztalk-get-started-get-started.svg"
        },
        {
            "Name": "InstallConfigure",
            "ConfigurationValue": "https://learn.microsoft.com/en-us/media/illustrations/biztalk-host-integration-install-configure.svg"
        }
    ],
    "Allocation": { 
        // Defines Users, Groups, or Percentiles for variant assignment
    }
    // Filters and other Feature fields
}

For more details on Variants, see here.

Telemetry

The feature management library now offers the ability to emit events containing information about a feature evaluation. This can be used to ensure a flag is running as expected, or to see which users were given which features and why they were given the feature. To enable this functionality, two things need to be done:

The flag needs to explicitly enable telemetry in its definition.
... (truncated)

3.5.0

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

  • No changes in this release.

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 3.5.0.

Enhancements

  • Introduced an overloaded extension method WithTargeting() for ASP.NET Core applications. It registers a default ITargetingContextAccessor that constructs user context based on the authenticated user of a request. #​466

3.4.0

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • All public classes no longer use init-only setters, ensuring compatibility with application using C# 7 or earlier. #​450

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 3.4.0.

3.3.1

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Bug fixes

  • Fixed a bug that TimeWindowFilter would be registered repeatedly when calling AddFeatureFilter<TimeWindowFilter> after the call of AddFeatureManagement(). #​447

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 3.3.1.

3.3.0

Microsoft.FeatureManagement Updates

The packages associated with this release are

Microsoft.FeatureManagement

Enhancements

  • Added a Recurrence option to the TimeWindow filter to support recurring time window. This enables scenarios where a feature flag is activated based on a recurrence pattern, such as every day after 5 PM or every Friday. See more details here. (#​266)
  • A LoggerFactory is no longer required when constructing built-in filters. (#​386)

Bug fixes

  • Fixed a possible null-reference exception when enumerating GetFeatureNamesAsync. (#​438)

Microsoft.FeatureManagement.AspNetCore

  • Updated Microsoft.FeatureManagement reference to 3.3.0.

Commits viewable in compare view.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump Microsoft.FeatureManagement.AspNetCore from 3.2.0 to 4.3.0
a6acb34 
---
updated-dependencies:
- dependency-name: Microsoft.FeatureManagement.AspNetCore
  dependency-version: 4.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Dec 8, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 22, 2025

Superseded by #136.

@dependabot dependabot bot closed this Dec 22, 2025
@dependabot dependabot bot deleted the dependabot/nuget/src/Web/Microsoft.FeatureManagement.AspNetCore-4.3.0 branch December 22, 2025 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant