chore(deps): update dependency microsoft.featuremanagement to v4.0.0-preview4

Open renovate[bot] opened this issue 1 year ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
Microsoft.FeatureManagement	`4.0.0-preview` -> `4.0.0-preview4`

Release Notes

microsoft/FeatureManagement-Dotnet (Microsoft.FeatureManagement)

`v4.0.0-preview4`

Compare Source

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 called "FeatureFlag" with tags contains feature evaluation information. #455

Breaking Changes

Variant and telemetry are no longer supported for .NET Feature Management schema. Please use Microsoft Feature Management schema to declare variant feature flag instead. #421

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

Added new AddApplicationInsightsTelemetryPublisher API to register a telemetry publisher to send events to Application Insights. #455

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

The TargetingTelemetryInitializer has been moved to the namespace Microsoft.FeatureManagement.Telemetry.ApplicationInsights. Developers no longer need to install Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore package for it. #467 The TargetingTelemetryInitializer now gets targeting information from current activity's baggage instead of HttpContext.Items.

Breaking Changes

The ApplicationInsightsTelemetryPublisher has been removed since ITelemetryPublisher interface was removed from Microsoft.FeatureManagement package. The feature flag telemetry pipeline is now integrated with .NET Acitivity instrumentation. #455

`v4.0.0-preview3`

Compare Source

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.

`v4.0.0-preview2`

Compare Source

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)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Mar 07 '24 19:03 renovate[bot]

This bump seems to break some of the tests for the ConfigCat provider. It might be worth waiting for a stable release since this is still in preview

@askpt: I'm pretty sure this is because there is some instability in ConfigCat provider tests. I've seen them fail on other PR's where they passed on a rerun.

Jun 24 '24 21:06 jenshenneberg