DOC Deprecate CMS GraphQL endpoints

silverstripe · Aug 18, 2024 · 18f8956 · 18f8956
1 parent 5b809f8
commit 18f8956
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/en/08_Changelogs/5.3.0.md b/en/08_Changelogs/5.3.0.md
@@ -163,6 +163,7 @@ From 6.0 onwards, tokens will never be regenerated during session renewal, and t
 - The [`RememberLoginHash::renew()`](api:SilverStripe\Security\RememberLoginHash::renew()) method has been deprecated without replacement, since the associated behaviour will be removed in 6.0.
   - The `onAfterRenewToken` extension point within this method will likely be replaced with a new extension point in 6.0.
 - The [`RememberLoginHash.replace_token_during_session_renewal`](api:SilverStripe\Security\RememberLoginHash->replace_token_during_session_renewal) configuration property has been added to allow disabling token regeneration during session renewal. This property will be removed in 6.0.
+- Code for the CMS GraphQL `admin` schema which provided endpoints for the CMS has been deprecated and will be removed in CMS 6. Functionality the GraphQL endpoints was responsible for has been replaced with regular Silverstripe controller endpoints instead. Extension hooks have been added to the new controller endpoints that return data to allow for customisation. Frontend schemas, such the `default` schema, will continue to work in CMS 6.
 
 ## Bug fixes