docs: changelog adjustments

changelog/9.0.0_2024-04-16/enhancement-extension-points → changelog/9.0.0_2024-04-16/change-extension-points

@@ -1,4 +1,6 @@
-Enhancement: Add extensionPoint concept
+Change: Add extensionPoint concept
+
+BREAKING CHANGE for developers: The `scopes` property has been removed from the `Extension` type in favour of the new `extensionPointIds` property.
 
 The extension system now allows developers to register extension points. An extension point defines the metadata for the
 integration of a certain extension type in a certain context. Examples for extension points are render targets for
@@ -7,10 +9,11 @@ menu), etc.
 
 Extensions can now specify that they are only valid for a certain or multiple extension points. This way a file action extension
 can e.g. specify to be rendered only in the context menu, but not in the batch actions. Consequently, the extension points
-concept is the next iteration of the `scopes` concept. The `scopes` concept will most likely be removed in a future release.
+concept is the next iteration of the `scopes` concept. The `scopes` concept has been removed from the codebase.
 
 Extension points can define if users should be able to choose preferences for the extension point. E.g. for the global progress
 bar extension point, users can choose which of the available progress bar extensions should be used, since the extension point
-only allows one extension to be active. At the moment we persist the user choice in the local storage of the browser.
+only allows one extension to be active. At the moment we persist the user choice in the localStorage of the browser.
 
 https://github.com/owncloud/web/pull/10443
+https://github.com/owncloud/web/pull/10758

changelog/9.0.0_2024-04-16/change-remove-deprecated-quick-actions-extension-point

@@ -1,6 +1,6 @@
 Change: Remove deprecated extension point for adding quick actions
 
-BREAKING CHANGE for developers: The old way of registering quick actions via the `quickaction` property of an app has been removed. Quick actions should be registered as extension via our extension registry. They need to be of type `action` and have the `files.quick-action` scope.
+BREAKING CHANGE for developers: The old way of registering quick actions via the `quickaction` property of an app has been removed. Quick actions should be registered as extension via our extension registry. They need to be of type `action` and have the `app.files.quick-action` extensionPointId.
 
 https://github.com/owncloud/web/pull/10102
 https://github.com/owncloud/web/pull/10223