-
Notifications
You must be signed in to change notification settings - Fork 22
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 4.0.0-preview4 - autoclosed #164
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
4 times, most recently
from
March 14, 2024 20:46
c5e89d9
to
654caaf
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
5 times, most recently
from
April 1, 2024 21:10
7106b6b
to
fd515af
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
4 times, most recently
from
April 8, 2024 17:18
6afb853
to
d318d35
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
from
April 11, 2024 01:31
d318d35
to
b955400
Compare
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
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
3 times, most recently
from
April 16, 2024 21:03
fe17c5b
to
2f159ed
Compare
askpt
requested changes
Apr 17, 2024
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.
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
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
3 times, most recently
from
April 24, 2024 19:56
c421db3
to
671c8da
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
from
April 30, 2024 13:41
671c8da
to
94e9e0e
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
14 times, most recently
from
August 22, 2024 13:42
26eac10
to
2c53aaa
Compare
renovate
bot
changed the title
chore(deps): update dependency microsoft.featuremanagement to v4.0.0-preview4
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4
Aug 28, 2024
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
2 times, most recently
from
September 6, 2024 12:53
b8dd2a1
to
b6750c7
Compare
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
2 times, most recently
from
September 17, 2024 20:03
21b9e09
to
f1ed85f
Compare
renovate
bot
changed the title
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4 - autoclosed
Sep 25, 2024
renovate
bot
changed the title
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4 - autoclosed
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4
Sep 25, 2024
renovate
bot
force-pushed
the
renovate/microsoft.featuremanagement-4.x
branch
from
September 25, 2024 16:44
f1ed85f
to
ba11068
Compare
renovate
bot
changed the title
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4
chore(deps): update dependency microsoft.featuremanagement to 4.0.0-preview4 - autoclosed
Sep 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
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
Acitivity
instrumentation. Feature manager now has anAcitvitySource
called "Microsoft.FeatureManagement". If telemetry is enabled for a feature flag, whenever the feature flag is evaluated, feature manager will start anActivity
and add anActivityEvent
with tags containing feature evaluation information. #455Breaking 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 andITelemetryPublisher
interface were removed. The feature flag telemetry pipeline is now integrated with .NETAcitivity
instrumentation. #455Microsoft.FeatureManagement.AspNetCore
Microsoft.FeatureManagement
reference to4.0.0-preview4
.Microsoft.FeatureManagement.Telemetry.ApplicationInsights
Microsoft.FeatureManagement
reference to4.0.0-preview4
.Enhancements
Introduced a new API
AddApplicationInsightsTelemetryPublisher
to register a feature flag telemetry publisher for Application Insights. #455Breaking Changes
The
TargetingTelemetryInitializer
type has been moved to this package from the now-deprecatedMicrosoft.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 APIAddApplicationInsightsTelemetryPublisher
for publishing feature flag telemetry to Application Insights. #455v4.0.0-preview3
Compare Source
Microsoft.FeatureManagement Updates
The packages associated with this release are
Microsoft.FeatureManagement
Enhancements
Microsoft.FeatureManagement.AspNetCore
Microsoft.FeatureManagement
reference to4.0.0-preview3
.Microsoft.FeatureManagement.Telemetry.ApplicationInsights
Breaking Changes
Updated the namespace for
ApplicationInsightsTelemetryPublisher
toMicrosoft.FeatureManagement.Telemetry
. In the future, developers using any of our offered telemetry publishers will no longer need to specify the service specific namespaces likeusing Microsoft.FeatureManagement.Telemetry.ApplicationInsights
.Updated the namespace for
TrackEvent
extension method ofTelemetryClient
toMicrosoft.ApplicationInsights
. The previous directiveusing Microsoft.FeatureManagement.Telemetry.ApplicationInsights
is no longer required when calling theTrackEvent
method.Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore
Microsoft.FeatureManagement
reference to4.0.0-preview3
.v4.0.0-preview2
Compare Source
Microsoft.FeatureManagement Updates
The packages associated with this release are
Microsoft.FeatureManagement
Enhancements
TargetingContext
property to theEvaluationEvent
. This allows feature evaluation events to accurately represent what the targeting context was at the time of feature evaluation. (#409)Microsoft.FeatureManagement.AspNetCore
Enhancements
TargetingHttpContextMiddleware
. It makes targeting information available fromHttpContext
on each request. (#409)Microsoft.FeatureManagement.Telemetry.ApplicationInsights
Enhancements
TargetingId
property to the feature evaluation events sent to Application Insights. TheTargetingId
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 sameTargetingId
. (#409)Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore
Enhancements
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.