From 6c8b52e291ba294c1893aa3378d7bcb4398d92f8 Mon Sep 17 00:00:00 2001 From: Seam Bot Date: Thu, 25 Sep 2025 18:07:54 +0000 Subject: [PATCH 1/2] feat: Update to @seamapi/types@1.589.0 --- package-lock.json | 8 ++++---- package.json | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package-lock.json b/package-lock.json index b6ab57b22..11e5bdd25 100644 --- a/package-lock.json +++ b/package-lock.json @@ -14,7 +14,7 @@ "@prettier/plugin-ruby": "^4.0.4", "@seamapi/blueprint": "^0.51.3", "@seamapi/smith": "^0.5.2", - "@seamapi/types": "1.588.0", + "@seamapi/types": "1.589.0", "@types/command-exists": "^1.2.3", "change-case": "^5.4.4", "command-exists": "^1.2.9", @@ -983,9 +983,9 @@ } }, "node_modules/@seamapi/types": { - "version": "1.588.0", - "resolved": "https://registry.npmjs.org/@seamapi/types/-/types-1.588.0.tgz", - "integrity": "sha512-RKRa5EyCu5qVlcTLpVrjnYo2vQcUcPO8/lB8McnZBYaA9H4DNat3yol6TKHJc/D+WDd0VnbY7T1jg2LGnavh+g==", + "version": "1.589.0", + "resolved": "https://registry.npmjs.org/@seamapi/types/-/types-1.589.0.tgz", + "integrity": "sha512-/sbRPLO808X6/i4TTBhWKgRCokBJC3pqEaK8BjAUhQyrM6qScKiZAVU2FHf1V+jX2U+syvqh4ZF3SMIHhnVEEQ==", "dev": true, "license": "MIT", "engines": { diff --git a/package.json b/package.json index ae4f52f1a..a51f0f473 100644 --- a/package.json +++ b/package.json @@ -32,7 +32,7 @@ "@prettier/plugin-ruby": "^4.0.4", "@seamapi/blueprint": "^0.51.3", "@seamapi/smith": "^0.5.2", - "@seamapi/types": "1.588.0", + "@seamapi/types": "1.589.0", "@types/command-exists": "^1.2.3", "change-case": "^5.4.4", "command-exists": "^1.2.9", From 2df89574d4b63434be88f19a0ecc7325ec78f60d Mon Sep 17 00:00:00 2001 From: Seam Bot Date: Thu, 25 Sep 2025 18:09:49 +0000 Subject: [PATCH 2/2] ci: Generate docs --- docs/api/_blueprint.json | 16 +++++++++++++++- docs/api/connected_accounts/update.md | 8 +++++++- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/docs/api/_blueprint.json b/docs/api/_blueprint.json index 3b0520208..2e562fd97 100644 --- a/docs/api/_blueprint.json +++ b/docs/api/_blueprint.json @@ -26103,7 +26103,7 @@ }, { "name": "custom_metadata", - "description": "Custom metadata that you want to associate with the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](../core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account.md) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](../core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata.md).", + "description": "Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](../core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account.md) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](../core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata.md).", "isRequired": false, "isDeprecated": false, "deprecationMessage": "", @@ -26114,6 +26114,20 @@ "hasDefault": false, "format": "record", "jsonType": "object" + }, + { + "name": "customer_key", + "description": "The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer.", + "isRequired": false, + "isDeprecated": false, + "deprecationMessage": "", + "isUndocumented": false, + "undocumentedMessage": "", + "isDraft": false, + "draftMessage": "", + "hasDefault": false, + "format": "string", + "jsonType": "string" } ] }, diff --git a/docs/api/connected_accounts/update.md b/docs/api/connected_accounts/update.md index cc697b400..017d5630a 100644 --- a/docs/api/connected_accounts/update.md +++ b/docs/api/connected_accounts/update.md @@ -183,7 +183,13 @@ Indicates whether newly-added devices should appear as [managed devices](../../c **`custom_metadata`** *Object* -Custom metadata that you want to associate with the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](../../core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account.md) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](../../core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata.md). +Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](../../core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account.md) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](../../core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata.md). + +--- + +**`customer_key`** *String* + +The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer. ---