refactor(tree): rename getAllowedContentIncompatibilities to getAllow…

.changeset/fifty-showers-divide.md

@@ -0,0 +1,34 @@
+---
+"fluid-framework": minor
+"@fluidframework/merge-tree": minor
+"@fluidframework/sequence": minor
+---
+---
+"section": deprecation
+---
+
+Unsupported merge-tree types and related exposed internals have been removed
+
+As part of ongoing improvements, several internal types and related APIs have been removed. These types are unnecessary for any supported scenarios and could lead to errors if used. Since directly using these types would likely result in errors, these changes are not likely to impact any Fluid Framework consumers.
+
+Removed types:
+- IMergeTreeTextHelper
+- MergeNode
+- ObliterateInfo
+- PropertiesManager
+- PropertiesRollback
+- SegmentGroup
+- SegmentGroupCollection
+
+In addition to removing the above types, they are no longer exposed through the following interfaces and their implementations: `ISegment`, `ReferencePosition`, and `ISerializableInterval`.
+
+Removed functions:
+- addProperties
+- ack
+
+Removed properties:
+- propertyManager
+- segmentGroups
+
+The initial deprecations of the now changed or removed types were announced in Fluid Framework v2.2.0:
+[Fluid Framework v2.2.0](https://github.com/microsoft/FluidFramework/blob/main/RELEASE_NOTES/2.2.0.md)

.changeset/fruity-sites-boil.md

@@ -0,0 +1,10 @@
+---
+"@fluidframework/runtime-definitions": minor
+---
+---
+"section": other
+---
+
+Changes to the batchBegin and batchEnd events on ContainerRuntime
+
+The 'batchBegin'/'batchEnd' events on ContainerRuntime indicate when a batch is beginning or finishing being processed. The `contents` property on the event argument `op` is not useful or relevant when reasoning over incoming changes at the batch level. Accordingly, it has been removed from the `op` event argument.

.changeset/icy-webs-help.md

@@ -0,0 +1,14 @@
+---
+"@fluidframework/container-runtime": minor
+"@fluidframework/runtime-definitions": minor
+"@fluidframework/test-runtime-utils": minor
+---
+---
+"section": legacy
+---
+
+"Remove `IFluidParentContext.ensureNoDataModelChanges` and its implementations
+
+- `IFluidParentContext.ensureNoDataModelChanges` has been removed. [prior deprecation commit](https://github.com/microsoft/FluidFramework/commit/c9d156264bdfa211a3075bdf29cde442ecea234c)
+
+- `MockFluidDataStoreContext.ensureNoDataModelChanges` has also been removed.

.changeset/loud-lemons-switch.md

@@ -0,0 +1,10 @@
+---
+"@fluidframework/runtime-utils": minor
+---
+---
+"section": feature
+---
+
+New compareFluidHandle function for comparing FluidHandles
+
+The new `compareFluidHandle` function has been added to allow comparing handles without having to inspect their internals.

.changeset/lovely-taxis-notice.md

@@ -0,0 +1,27 @@
+---
+"fluid-framework": minor
+"@fluidframework/tree": minor
+---
+---
+"section": tree
+---
+
+SharedTree event listeners that implement `Listenable` now allow deregistration of event listeners via an `off()` function.
+
+The ability to deregister events via a callback returned by `on()` remains the same.
+Both strategies will remain supported and consumers of SharedTree events may choose which method of deregistration they prefer in a given instance.
+
+```typescript
+// The new behavior
+function deregisterViaOff(view: TreeView<MySchema>): {
+	const listener = () => { /* ... */ };
+	view.events.on("commitApplied", listener); // Register
+	view.events.off("commitApplied", listener); // Deregister
+}
+
+// The existing behavior (still supported)
+function deregisterViaCallback(view: TreeView<MySchema>): {
+	const off = view.events.on("commitApplied", () => { /* ... */ }); // Register
+	off(); // Deregister
+}
+```

.changeset/moody-flies-fly.md

@@ -0,0 +1,26 @@
+---
+"fluid-framework": minor
+"@fluidframework/tree": minor
+---
+---
+"section": tree
+---
+
+Allow constructing recursive maps from objects
+
+Previously only non-recursive maps could be constructed from objects.
+Now all maps nodes can constructed from objects:
+
+```typescript
+class MapRecursive extends sf.mapRecursive("Map", [() => MapRecursive]) {}
+{
+	type _check = ValidateRecursiveSchema<typeof MapRecursive>;
+}
+// New:
+const fromObject = new MapRecursive({ x: new MapRecursive() });
+// Existing:
+const fromIterator = new MapRecursive([["x", new MapRecursive()]]);
+const fromMap = new MapRecursive(new Map([["x", new MapRecursive()]]));
+const fromNothing = new MapRecursive();
+const fromUndefined = new MapRecursive(undefined);
+```

.changeset/nice-flies-brake.md

@@ -0,0 +1,32 @@
+---
+"@fluidframework/aqueduct": minor
+"@fluidframework/container-definitions": minor
+"@fluidframework/container-loader": minor
+"@fluidframework/container-runtime": minor
+"@fluidframework/container-runtime-definitions": minor
+"@fluidframework/datastore": minor
+"@fluidframework/devtools-core": minor
+"@fluidframework/fluid-static": minor
+"@fluidframework/runtime-definitions": minor
+"@fluidframework/runtime-utils": minor
+"@fluid-private/test-end-to-end-tests": minor
+"@fluidframework/test-runtime-utils": minor
+"@fluidframework/test-utils": minor
+---
+---
+"section": legacy
+---
+
+The inbound and outbound properties have been removed from IDeltaManager
+
+The inbound and outbound properties were [deprecated in version 2.0.0-rc.2.0.0](https://github.com/microsoft/FluidFramework/blob/main/RELEASE_NOTES/2.0.0-rc.2.0.0.md#container-definitions-deprecate-ideltamanagerinbound-and-ideltamanageroutbound) and have been removed from `IDeltaManager`.
+
+`IDeltaManager.inbound` contained functionality that could break core runtime features such as summarization and processing batches if used improperly. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
+
+Similarly, `IDeltaManager.outbound` contained functionality that could break core runtime features such as generation of batches and chunking. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
+
+#### Alternatives
+
+- Alternatives to `IDeltaManager.inbound.on("op", ...)` are `IDeltaManager.on("op", ...)`
+- Alternatives to calling `IDeltaManager.inbound.pause`, `IDeltaManager.outbound.pause` for `IContainer` disconnect use `IContainer.disconnect`.
+- Alternatives to calling `IDeltaManager.inbound.resume`, `IDeltaManager.outbound.resume` for `IContainer` reconnect use `IContainer.connect`.

.changeset/rude-views-bake.md

@@ -0,0 +1,30 @@
+---
+"fluid-framework": minor
+"@fluidframework/merge-tree": minor
+"@fluidframework/sequence": minor
+---
+---
+"section": legacy
+---
+
+MergeTree `Client` Legacy API Removed
+
+The `Client` class in the merge-tree package has been removed. Types that directly or indirectly expose the merge-tree `Client` class have also been removed.
+
+The removed types were not meant to be used directly, and direct usage was not supported:
+
+- AttributionPolicy
+- IClientEvents
+- IMergeTreeAttributionOptions
+- SharedSegmentSequence
+- SharedStringClass
+
+Some classes that referenced the `Client` class have been transitioned to interfaces. Direct instantiation of these classes was not supported or necessary for any supported scenario, so the change to an interface should not impact usage. This applies to the following types:
+
+- SequenceInterval
+- SequenceEvent
+- SequenceDeltaEvent
+- SequenceMaintenanceEvent
+
+The initial deprecations of the now changed or removed types were announced in Fluid Framework v2.4.0:
+[Several MergeTree Client Legacy APIs are now deprecated](https://github.com/microsoft/FluidFramework/blob/main/RELEASE_NOTES/2.4.0.md#several-mergetree-client-legacy-apis-are-now-deprecated-22629)