diff --git a/website/docs/change-requests.mdx b/website/docs/change-requests.mdx index 2985a089..765e6016 100644 --- a/website/docs/change-requests.mdx +++ b/website/docs/change-requests.mdx @@ -176,7 +176,7 @@ This option closes the entire change request. Choose this when the conflict cann The approval flow currently applies to feature flag changes only. The following actions do not require a change request or approval: -- The features are only available for V2 configs. See the [Config V2 Migration Guide](../advanced/config-v2-migration-guide). +- The features are only available for V2 configs and are not supported for V1 configs. See the [Config V2 Migration Guide](../advanced/config-v2-migration-guide). - Creating or deleting a feature flag. - Changes to predefined variations. - Changes to segments. diff --git a/website/docs/news.mdx b/website/docs/news.mdx index 2eaf5465..0248bd97 100644 --- a/website/docs/news.mdx +++ b/website/docs/news.mdx @@ -11,6 +11,34 @@ Here, you'll find all the latest updates, enhancements, and new features we've a {/* This page must be in sync with the news page on the Dashboard: https://github.com/configcat/app/blob/master/src/app/home-module/news/news.component.html */} +## Introducing: Approval Flow & Scheduled Changes + +#### Aug 27, 2026 + +We're excited to roll out our latest features: now you can require feature flag changes to go through peer review before publishing, schedule them to be applied automatically at a specific time, or even both. + +This is made possible by _change requests_, which let you prepare feature flag changes without publishing them right away. + +
+
+
+
+