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.

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

chore(deps): update dependency microsoft.featuremanagement to v4.0.0-preview3 #164

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 7, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Microsoft.FeatureManagement 4.0.0-preview -> 4.0.0-preview3 age adoption passing confidence

Release Notes

microsoft/FeatureManagement-Dotnet (Microsoft.FeatureManagement)

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner March 7, 2024 19:59
@renovate renovate bot added the renovate label Mar 7, 2024
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 4 times, most recently from c5e89d9 to 654caaf Compare March 14, 2024 20:46
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 5 times, most recently from 7106b6b to fd515af Compare April 1, 2024 21:10
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 4 times, most recently from 6afb853 to d318d35 Compare April 8, 2024 17:18
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch from d318d35 to b955400 Compare April 11, 2024 01:31
@renovate renovate bot changed the title chore(deps): update dependency microsoft.featuremanagement to v4.0.0-preview2 chore(deps): update dependency microsoft.featuremanagement to v4.0.0-preview3 Apr 11, 2024
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 3 times, most recently from fe17c5b to 2f159ed Compare April 16, 2024 21:03
@renovate renovate bot requested a review from a team as a code owner April 16, 2024 21:03
Copy link
Member

@askpt askpt left a comment

Choose a reason for hiding this comment

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

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

@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 3 times, most recently from c421db3 to 671c8da Compare April 24, 2024 19:56
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch from 671c8da to 94e9e0e Compare April 30, 2024 13:41
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch from 94e9e0e to 4c285c8 Compare April 30, 2024 15:00
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 4 times, most recently from 9a620f5 to d9a9da8 Compare May 13, 2024 17:25
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 5 times, most recently from 065bdec to f2cff69 Compare May 17, 2024 19:18
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch from f2cff69 to fccd60d Compare May 30, 2024 15:51
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 4 times, most recently from a2dc27f to c158cd8 Compare June 13, 2024 11:48
@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch 6 times, most recently from eebcbf9 to 3155480 Compare June 24, 2024 21:39
@jenshenneberg
Copy link
Contributor

jenshenneberg commented Jun 24, 2024

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.

@renovate renovate bot force-pushed the renovate/microsoft.featuremanagement-4.x branch from 3155480 to d456c7b Compare June 24, 2024 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants