docs(v1.3.0): update docs for release

docs-website/docusaurus.config.js

@@ -145,6 +145,14 @@ module.exports = {
               type: 'html',
               value: '<div class="dropdown__link"><b>Archived versions</b></div>',
             },
+            {
+              value: `
+                     <a class="dropdown__link" href="https://docs-website-j2wcc9mjw-acryldata.vercel.app/docs/features">1.3.0
+                     <svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg>
+                     </a>
+                     `,
+              type: "html",
+            },
             {
               value: `
                      <a class="dropdown__link" href="https://docs-website-t9sv4w3gr-acryldata.vercel.app/docs/features">1.0.0

docs-website/versions.json

@@ -1,3 +1,3 @@
 [
-  "1.1.0"
+  "1.3.0"
 ]

docs/how/updating-datahub.md

@@ -37,6 +37,19 @@ This file documents any backwards-incompatible changes in DataHub and assists pe
   - `browsePaths` aspect replaced with `browsePathsV2`
   - In `Dashboard` entitiy and `dashboardInfo` aspect, `charts` property (deprecated) is replaced with `chartEdges`
   - Only emits MCPs
+
+### Known Issues
+
+### Potential Downtime
+
+### Deprecations
+
+### Other Notable Changes
+
+## 1.3.0
+
+### Breaking Changes
+
 - #14580: (Ingestion) The redshift lineage v1 implementation (`RedshiftLineageExtractor`) has been removed, as lineage v2 (`RedshiftSqlLineageV2`) implementation has been default for a while already. As an effect `use_lineage_v2` config has also been removed along with all lineage v1 references and tests have been updated to v2 implementation. This should not impact most users as change is isolated in redshift ingestion source only.
 - #14014: The `acryl-datahub` now requires pydantic v2. Support for pydantic v1 has been dropped and users must upgrade to pydantic v2 when using DataHub python package.
   - As a side effect, this upgrade in pydantic version has implicit consequences for `iceberg` ingestion source. If it is run from CLI and `datahub` CLI was installed with all extras (`acryl-datahub[all]`), then `pyiceberg` has been kept at `0.4.0` version in such environment, just to satisfiy the pydantic v1 restriction. However now, `pyiceberg` will be installed in the newest available version. While this is a breaking change in the behaviour, versions `>0.4.0` have been used for some time by Managed Ingestion.

metadata-io/src/main/java/com/linkedin/metadata/search/utils/ESUtils.java

@@ -1278,6 +1278,7 @@ public static void cleanupPointInTime(SearchClientShim<?> client, String pitId,
             // succeeded
             log.debug("Successfully cleaned up PIT {} for {}", pitId, context);
           }
+          break;
         case ELASTICSEARCH_7:
           {
             // For Elasticsearch, use the low-level client to delete PIT
@@ -1295,6 +1296,7 @@ public static void cleanupPointInTime(SearchClientShim<?> client, String pitId,
                   response.getStatusLine().getStatusCode());
             }
           }
+          break;
       }
     } catch (Exception e) {
       log.warn("Error cleaning up PIT {} for {}: {}", pitId, context, e.getMessage());