2.3.1

What's Changed

• Bump flatted from 3.3.3 to 3.4.2 in /src/feature-management by @dependabot[bot] in #153
• Bump flatted from 3.3.3 to 3.4.2 in /src/feature-management-applicationinsights-browser by @dependabot[bot] in #154
• Fix missing filter evaluation by @linglingye001 in #158
• Bump vite from 7.1.11 to 7.3.2 in /src/feature-management by @dependabot[bot] in #157
• Bump picomatch in /src/feature-management-applicationinsights-node by @dependabot[bot] in #156
• Bump picomatch from 2.3.1 to 2.3.2 in /src/feature-management by @dependabot[bot] in #155
• Bump flatted from 3.3.3 to 3.4.2 in /src/feature-management-applicationinsights-node by @dependabot[bot] in #161
• Agent skill for release by @linglingye001 in #159
• Version bump to 2.3.1 on main by @Copilot in #162

New Contributors

• @Copilot made their first contribution in #162

Full Changelog: 2.3.0...2.3.1

2.3.0

What's Changed

• Upgrade dev dependency by @zhiyuanliang-ms in #128
• Use vitest for browser test by @zhiyuanliang-ms in #129
• Bump vite from 7.1.4 to 7.1.5 in /src/feature-management by @dependabot[bot] in #130
• Bump vite from 7.1.5 to 7.1.11 in /src/feature-management by @dependabot[bot] in #132
• Bump playwright from 1.55.0 to 1.56.1 in /src/feature-management by @dependabot[bot] in #131
• Update rollup by @zhiyuanliang-ms in #133
• Export IFeatureFilterEvaluationContext by @linglingye001 in #135
• Bump js-yaml from 4.1.0 to 4.1.1 in /src/feature-management by @dependabot[bot] in #136
• Bump js-yaml from 4.1.0 to 4.1.1 in /src/feature-management-applicationinsights-browser by @dependabot[bot] in #137
• Bump js-yaml from 4.1.0 to 4.1.1 in /src/feature-management-applicationinsights-node by @dependabot[bot] in #138
• Bump glob from 11.0.3 to 11.1.0 in /src/feature-management-applicationinsights-node by @dependabot[bot] in #140
• Bump glob from 11.0.3 to 11.1.0 in /src/feature-management-applicationinsights-browser by @dependabot[bot] in #139
• Bump minimatch from 3.1.2 to 3.1.5 in /src/feature-management by @dependabot[bot] in #143
• Bump minimatch from 3.1.2 to 3.1.5 in /src/feature-management-applicationinsights-node by @dependabot[bot] in #144
• Bump rollup from 4.50.0 to 4.59.0 in /src/feature-management by @dependabot[bot] in #145
• Bump glob in /src/feature-management by @dependabot[bot] in #146
• Bump minimatch from 3.1.2 to 3.1.5 in /src/feature-management-applicationinsights-browser by @dependabot[bot] in #147
• Bump rollup from 4.50.0 to 4.59.0 in /src/feature-management-applicationinsights-node by @dependabot[bot] in #148
• version bump 2.3.0 by @zhiyuanliang-ms in #149

Full Changelog: 2.2.0...2.3.0

2.2.0

• @microsoft/feature-management 2.2.0
• @microsoft/feature-management-applicationinsights-browser 2.2.0
• @microsoft/feature-management-applicationinsights-node 2.2.0

@microsoft/feature-management

Enhancements

• Added a Recurrence option to the TimeWindowFilter 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 the how to Time Window Filter document for more details.

@microsoft/feature-management-applicationinsights-browser

• Updated @microsoft/feature-management dependency to 2.2.0.

@microsoft/feature-management-applicationinsights-node

• Updated @microsoft/feature-management dependency to 2.2.0.

2.1.0

• @microsoft/feature-management 2.1.0
• @microsoft/feature-management-applicationinsights-browser 2.1.0
• @microsoft/feature-management-applicationinsights-node 2.1.0

@microsoft/feature-management

Enhancements

• Stablized the targeting context accessor. You can configure an ITargetingContextAccessor when initializing the FeatureManager through FeatureManagerOptions.targetingContextAccessor. #93

• Stablized the feature evaluation event properties. The shape of the object returned by createFeatureEvaluationEventProperties contains the following fields: "Version", "FeatureName", "Enabled", "TargetingId", "Variant", "VariantAssignmentReason", "DefaultWhenEnabled" and "VariantAssignmentPercentage".

@microsoft/feature-management-applicationinsights-browser

• Updated @microsoft/feature-management dependency to 2.1.0.

• Stablized createTargetingTelemetryInitializer function to enable targeting id to be attached to Application Insights telemetry. #98

@microsoft/feature-management-applicationinsights-node

• Updated @microsoft/feature-management dependency to 2.1.0.

• Stablized createTargetingTelemetryProcessor function to enable targeting id to be attached to Application Insights telemetry. #98

2.1.0-preview.1

The packages associated with this release are

• @microsoft/feature-management 2.1.0-preview.1
• @microsoft/feature-management-applicationinsights-browser 2.1.0-preview.1
• @microsoft/feature-management-applicationinsights-node 2.1.0-preview.1

@microsoft/feature-management

Enhancements

• Introduced ITargetingContextAccessor to allow FeatureManager to get ambient targeting context in the server scenario. You can configure a targeting context accessor when initializing the FeatureManager through FeatureManagerOptions.targetingContextAccessor. #93

@microsoft/feature-management-applicationinsights-browser

• Updated @microsoft/feature-management dependency to 2.1.0-preview.1.

Enhancements

• Added createTargetingTelemetryInitializer function to enable targeting id to be attached to Application Insights telemetry. #98

@microsoft/feature-management-applicationinsights-node

• Updated @microsoft/feature-management dependency to 2.1.0-preview.1.

Enhancements

• Added createTargetingTelemetryProcessor function to enable targeting id to be attached to Application Insights telemetry. #98

2.0.2

The packages associated with this release are

• @microsoft/feature-management 2.0.2
• @microsoft/feature-management-applicationinsights-browser 2.0.2
• @microsoft/feature-management-applicationinsights-node 2.0.2

@microsoft/feature-management

• Updated README

@microsoft/feature-management-applicationinsights-browser

• Updated README

@microsoft/feature-management-applicationinsights-node

• Updated README

2.0.1

The packages associated with this release are

• @microsoft/feature-management 2.0.1
• @microsoft/feature-management-applicationinsights-browser 2.0.1
• @microsoft/feature-management-applicationinsights-node 2.0.1

@microsoft/feature-management

• Updated README

@microsoft/feature-management-applicationinsights-browser

• Updated README

## @microsoft/feature-management-applicationinsights-node

• Updated README

2.0.0

Microsoft Feature Management Updates

The packages associated with this release are

• @microsoft/feature-management 2.0.0
• @microsoft/feature-management-applicationinsights-browser 2.0.0
• @microsoft/feature-management-applicationinsights-node 2.0.0

@microsoft/feature-management

Enhancements

This is the first stable release of the following features.

• 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 getVariant method of FeatureManager has been introduced to evaluate the assigned variant based on the variant feature flag configuration and targeting context. #13

• 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.

  The new onFeatureEvaluated constructor parameter of FeatureManager allows you to set a custom callback for all feature evaluations. This hook can be used to publish telemetry. You can call createTelemetryPublisher API from @microsoft/feature-management-applicationinsights-browser and @microsoft/feature-management-applicationinsights-node packages to publish feature evaluation event to Application Insights. #36

Bug Fixes

• Fixed a bug that caused error when calling getFeatureFlags and listFeatureNames. #74

@microsoft/feature-management-applicationinsights-browser

Enhancements

This is the first stable release of the following features.

• A createTelemetryPublisher function that has been added that enables feature evaluation telemetry to be published to Application Insights.

• A TrackEvent function has been added to enable sending custom events embedded with targeting information to Application Insights. This function is meant to be used in place of the Application Insights package's standard TrackEvent call.

@microsoft/feature-management-applicationinsights-node

Enhancements

This is the first stable release of the following features.

• A createTelemetryPublisher function that has been added that enables feature evaluation telemetry to be published to Application Insights.

• A TrackEvent function has been added to enable sending custom events embedded with targeting information to Application Insights. This function is meant to be used in place of the Application Insights package's standard TrackEvent call.

2.0.0-preview.2

Microsoft Feature Management Updates

The packages associated with this release are

• @microsoft/feature-management 2.0.0-preview.2
• @microsoft/feature-management-applicationinsights-browser 2.0.0-preview.2

@microsoft/feature-management

• No changes in this release.

@microsoft/feature-management-applicationinsights-browser

• Fixed a bug that caused TargetingId in telemetry to be "undefined". #59

2.0.0-preview.1

Microsoft Feature Management Updates

The packages associated with this release are

• @microsoft/feature-management 2.0.0-preview.1
• @microsoft/feature-management-applicationinsights-browser 2.0.0-preview.1

@microsoft/feature-management

• Added support for 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).

• Added support for telemetry in feature flags. Telemetry is a powerful feature that allows you to track how your feature flags are being used. It provides insights into the effectiveness of your feature flags and helps you make data-driven decisions. Telemetry is particularly useful for feature experimentation (also known as A/B testing) and feature rollouts.

@microsoft/feature-management-applicationinsights-browser

• Added a built-in method to create telemetry publisher with Application Insights.

• Added a built-in TrackEvent method to send custom event to Application Insights with targeting id attached.