Code References and safe flag cleanup
Run the public @maxlona/code-refs scanner in CI to connect flag keys with repository, file, and line locations. Cleanup combines those reports with recent evaluations, lifecycle state, serving behavior, and dependencies so teams can remove stale branches before archiving a flag.
Set up Code References →Editing flags under automation
Flags stay editable while automation runs. Each environment shows the plan that controls it and its next step. Saving a change there asks before it pauses the plan, and the plan pauses immediately so its next step can't overwrite you. Turning a flag off stays one click. A paused plan shows yellow Suspended with who changed what (red Errored is kept for failed steps), and Resume lists what changed since the pause. Configuration and Automation are now tabs under one flag header, with Suspend and Resume on the flag page.
Read about editing under automation →Per-flag Environments
Choose which environments each flag uses. Mark an environment as opt-in so it only appears on the flags that need it, and use Manage environments on any flag to add an opt-in environment or remove one it never ships to. Existing flags keep every environment they use today. Dependencies stay safe: a parent flag must cover every environment of the flags that depend on it, and any change that would break that asks you how to fix it.
Read about environments →Feature Flag Automation
Build and manage scheduled activations, progressive rollouts, environment promotions, consumption-based releases, regional launches, temporary flags, and release-retirement plans. Validate plans before activation, suspend and resume safely, prevent conflicting automations, and follow every active workflow from the flag lifecycle summary.
Explore Feature Flag Automation →Flag Dependency Visualization
The dependency graph on each flag now flags dependency safety issues directly on the diagram — prerequisites that are disabled, archived, or missing are called out with highlighted nodes and edges so risky chains are obvious at a glance.
End of Enrollment
Lock in who’s enrolled in a flag without turning it off. Set an End of Enrollment date on any stage and everyone already admitted keeps the flag forever — anyone new after the cutoff evaluates to off.
Feature Flag Notes
Manage, create, and track notes directly on your feature flags to improve team communication, document important decisions, and keep context close to the features you’re managing.
Webhook Authentication
Webhooks now support flexible authentication options, including API Keys as custom HTTP headers, Bearer Tokens, and authentication values passed through the Query String.
Developer SDKs
Added comprehensive SDK packages for developers, including support for .NET / C# and NPM / JavaScript. Developer resources and packages are available under /docs/sdk.
Comprehensive Swagger API Docs
Added a comprehensive Swagger documentation page covering complete flag evaluation and configuration APIs, making it easier for developers to explore and integrate with the platform.
Postman API Consumption Collection
Added a ready-to-use Postman HTTP API Examples showing how to consume the actual backend APIs for feature flag evaluation. Preconfigured variables and Management Key authentication make it easy to connect, evaluate flags, and integrate the APIs into your application.
Notification Management Scopes
Added new notification management scopes for Webhooks and Approvals evaluations, providing more granular control over notification permissions and management.
Contact Us: Support History
The Contact Us page now shows your recent submissions and complete conversation history, including previously submitted support requests and their status with real-time updates.