docs(updating-datahub): update docs for v0.12.1 (datahub-project#9441)

docs/how/updating-datahub.md

@@ -7,15 +7,26 @@ This file documents any backwards-incompatible changes in DataHub and assists pe
 ### Breaking Changes
 
 - Updating MySQL version for quickstarts to 8.2, may cause quickstart issues for existing instances.
+
+### Potential Downtime
+
+### Deprecations
+
+### Other Notable Changes
+
+## 0.12.1
+
+### Breaking Changes
+
 - #9244: The `redshift-legacy` and `redshift-legacy-usage` sources, which have been deprecated for >6 months, have been removed. The new `redshift` source is a superset of the functionality provided by those legacy sources.
 - `database_alias` config is no longer supported in SQL sources namely - Redshift, MySQL, Oracle, Postgres, Trino, Presto-on-hive. The config will automatically be ignored if it's present in your recipe. It has been deprecated since v0.9.6.
 - #9257: The Python SDK urn types are now autogenerated. The new classes are largely backwards compatible with the previous, manually written classes, but many older methods are now deprecated in favor of a more uniform interface. The only breaking change is that the signature for the director constructor e.g. `TagUrn("tag", ["tag_name"])` is no longer supported, and the simpler `TagUrn("tag_name")` should be used instead.
   The canonical place to import the urn classes from is `datahub.metadata.urns.*`. Other import paths, like `datahub.utilities.urns.corpuser_urn.CorpuserUrn` are retained for backwards compatibility, but are considered deprecated.
 - #9286: The `DataHubRestEmitter.emit` method no longer returns anything. It previously returned a tuple of timestamps.
 - #8951: A great expectations based profiler has been added for the Unity Catalog source.
-To use the old profiler, set `method: analyze` under the `profiling` section in your recipe.
-To use the new profiler, set `method: ge`. Profiling is disabled by default, so to enable it,
-one of these methods must be specified.
+  To use the old profiler, set `method: analyze` under the `profiling` section in your recipe.
+  To use the new profiler, set `method: ge`. Profiling is disabled by default, so to enable it,
+  one of these methods must be specified.
 
 ### Potential Downtime