1.6.1 release notes

docs/platform/enterprise-setup/multi-region.md

@@ -111,26 +111,26 @@ Once you have a region, you create a data plane within it.
 <details>
   <summary>Request</summary>
 
-Send a POST request to /v1/regions/`<REGION_ID>`/dataplanes.
+Send a POST request to /v1/dataplanes.
 
 ```bash
-curl --request POST \
-  --url https://example.com/api/public/v1/regions/116a49ab-b04a-49d6-8f9e-4d9d6a4189cc/dataplanes \
-  --header 'authorization: Bearer $TOKEN' \
-  --header 'content-type: application/json' \
-  --data '{
-  "name": "aws-us-west-3-dp-8"
-}'
+curl -X POST https://example.com/api/public/v1/dataplanes \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -d '{
+    "name": "My Data Plane"
+    "regionId": "780d5bd9-a8a0-43cf-8b35-cc2061ad8319"
+  }'
 ```
 
 Include the following parameters in your request.
 
 | Body parameter | Required? | Description                                                                                                         |
 | -------------- | --------- | ------------------------------------------------------------------------------------------------------------------- |
 | `name`         | Required  | The name of your data plane. For simplicity, you might want to name it based on the region in which you created it. |
-| `enabled`      | Optional  | Defaults to true. Set this to `false` if you don't want this data plane enabled.                                        |
+| `regionId`     | Optional  | The region this data plane belongs to.                                                                              |
 
-For additional request examples, see [the API reference](https://reference.airbyte.com/reference/regions#/).
+For additional request examples, see [the API reference](https://reference.airbyte.com/reference/dataplanes#/).
 
 </details>
 

docs/release_notes/v-1.6.md

@@ -118,3 +118,17 @@ Airbyte now requires that stream identifiers be unique across Airbyte connection
 A common scenario looks like this: you have multiple accounts for the same source API and want to sync all this data to a single table in your destination. Although convenient, doing this carried a risk of data loss as multiple connections clashed with each other while writing to the same table.
 
 After careful consideration, Airbyte has stopped supporting this. You must use a unique prefix for each stream or a unique namespace in each connection. Then, you can combine your tables downstream of Airbyte. [Learn more >](/platform/using-airbyte/configuring-schema#stream-uniqueness)
+
+## Patches
+
+### 1.6.1
+
+Version 1.6.1 was released April 30, 2025.
+
+- Fixed [issue #58587](https://github.com/airbytehq/airbyte/issues/58587), which caused some 1.6.0 installs and upgrades using abctl and helm to fail.
+
+- Self-Managed Enterprise customers can create, update, delete, and list data planes using the new `/dataplane` endpoint. Previously, data plane endpoints were under `/region`. For more information about creating data planes, see [Multiple region deployments](/platform/enterprise-setup/multi-region).
+
+- Data planes and regions are automatically enabled when you create them. Previously, you had to set this manually.
+
+- Removed an unnecessary line from the log in workload-launcher, because it caused a variety of problems.