MTM-61884: Change log for tenant context operation api

content/change-logs/analytics/cumulocity-undefined-notifications-tenant-context-operations-wildcard.md

@@ -0,0 +1,16 @@
+---
+date: 2025-01-10
+title: Changes to Notifications 2.0 tenant context subscriptions with no API filter
+change_type:
+  - value: change-3BQrQ6adS
+    label: API change
+product_area: Platform services
+component:
+  - value: component-JlFdtOPva
+    label: REST API
+build_artifact:
+  - value: tc-QHwMfWtBk7
+    label: cumulocity
+---
+
+As previously announced, see [CD Release](https://cumulocity.com/docs/change-logs/?change-type=.change-type-api-change#cumulocity-undefined-notifications-tenant-context-operations-wildcard-announcement), applications utilizing the wildcard API selector in Notifications 2.0 tenant context subscriptions will now start receiving operations updates in addition to the updates they were already receiving. This change applies to both existing and new tenant context subscriptions.

content/change-logs/platform-services/cumulocity-undefined-notifications-tenant-context-event-type-filter.md

@@ -0,0 +1,18 @@
+---
+date: 2025-01-10
+title: changes to Notifications 2.0 tenant context subscriptions with event API filter
+change_type:
+  - value: change-3BQrQ6adS
+    label: API change
+product_area: Platform services
+component:
+  - value: component-JlFdtOPva
+    label: REST API
+build_artifact:
+  - value: tc-QHwMfWtBk7
+    label: cumulocity
+---
+
+Notifications 2.0 subscriptions may specify the {{< product-c8y-iot >}}  APIs to subscribe to, for example `events` or `measurements`.
+If the events API is specifically included as the only API in a Subscription's filter, a typeFilter was also required be set in that filter to make the subscription work.
+The restriction requiring a typeFilter when subscribing to the events API has been removed. Subscriptions to the events API can now be created without specifying a typeFilter