@tailor-platform/sdk 2.22.0 → 2.23.0

package/docs/cli/application.md

@@ -167,12 +167,20 @@ Before applying changes, `deploy` shows a preview of the planned resource change
 - `-` means the resource will be deleted
 - `±` means the resource will be replaced
 
+An update marked `[forced by SDK version]` shows no configuration difference from what is deployed. It is applied again only because resources of this application were last deployed with a different SDK version.
+
 After the detailed list, a summary line is printed:
 
 ```text
 Plan: 5 to create, 3 to update, 1 to delete
 ```
 
+When some updates are forced by the SDK version, the summary line also shows how many:
+
+```text
+Plan: 0 to create, 12 to update (11 forced by SDK version), 0 to delete
+```
+
 Use `--dry-run` to preview the plan without applying anything. In dry-run mode the plan is written to **stdout**, so it can be captured in CI without `2>&1`:
 
 ```bash
@@ -189,9 +197,16 @@ Pass the global `--json` / `-j` flag to get machine-readable output.
 
 ```json
 {
-  "summary": { "create": 2, "update": 1, "delete": 0, "replace": 0 },
+  "summary": { "create": 2, "update": 2, "delete": 0, "replace": 0, "forcedBySdkVersion": 1 },
   "changes": [
-    { "action": "create", "name": "Order", "labels": ["table"], "namespace": "tailordb" }
+    { "action": "create", "name": "Order", "labels": ["table"], "namespace": "tailordb" },
+    {
+      "action": "update",
+      "name": "Customer",
+      "labels": ["table"],
+      "namespace": "tailordb",
+      "forcedBySdkVersion": true
+    }
   ],
   "warnings": [
     { "type": "unmanaged", "resourceType": "tailorDB", "name": "LegacyType" },
@@ -201,15 +216,18 @@ Pass the global `--json` / `-j` flag to get machine-readable output.
 }
 ```
 
-- `summary` — counts of each change type.
-- `changes` — planned resource changes, each with `action`, `name`, and optional `labels` / `namespace`.
+- `summary` — counts of each change type. `forcedBySdkVersion` counts the updates forced by the SDK version, which are also included in `update`.
+- `changes` — planned resource changes, each with `action`, `name`, and optional `labels` / `namespace`. An update forced by the SDK version also has `forcedBySdkVersion: true`.
 - `warnings` — resources not in config (`type: "unmanaged"`) or secrets with missing values (`type: "skippedSecret"`). Unmanaged resources require confirmation in apply mode (apply is cancelled if declined); skipped secrets are non-blocking.
 - `conflicts` — resources owned by another application that conflict with the current config. Require confirmation in apply mode; apply is cancelled if declined.
 
 **Apply** (`--json`): writes a JSON object to stdout:
 
 ```json
-{ "summary": { "create": 1, "update": 2, "delete": 0, "replace": 0 }, "status": "applied" }
+{
+  "summary": { "create": 1, "update": 2, "delete": 0, "replace": 0, "forcedBySdkVersion": 0 },
+  "status": "applied"
+}
 ```
 
 ## remove

package/docs/cli/function.md

@@ -129,9 +129,9 @@ $ tailor function logs <execution-id> --follow
 
 **Notes**
 
-Execution details include `logEntries`, the structured log lines (message, severity, timestamp) recorded while the function ran. They are available while the execution is still running, whereas the flat `logs` string is filled in only after completion. The human-readable view shows the structured entries when present and falls back to `logs` otherwise.
+Execution details include `logEntries`, the structured log lines (message, severity, timestamp) recorded while the function ran. They are available while the execution is still running. The `logs` string joins their messages with newlines.
 
-Use `--follow` to keep polling a running execution and print new log entries as they arrive until it completes. Polling continues while the execution is suspended at a wait point, and indefinitely unless `--timeout` is set. On environments where no structured entries are returned, `--follow` shows the flat `logs` string once the execution completes. With `--json`, `--follow` waits for completion and then emits the final execution details once.
+Use `--follow` to keep polling a running execution and print new log entries as they arrive until it completes. Polling continues while the execution is suspended at a wait point, and indefinitely unless `--timeout` is set. With `--json`, `--follow` waits for completion and then emits the final execution details once.
 
 When viewing a specific execution that failed, the command displays error details with the stack trace mapped back to your original source files (clickable file links and code snippets, matching `function run` output).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "2.22.0",
+  "version": "2.23.0",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {
@@ -191,7 +191,7 @@
     "pathe": "2.0.3",
     "pgsql-ast-parser": "12.0.2",
     "pkg-types": "2.3.3",
-    "rolldown": "1.2.9",
+    "rolldown": "1.2.11",
     "semver": "7.8.5",
     "sql-highlight": "6.1.0",
     "std-env": "4.2.0",
@@ -215,7 +215,7 @@
     "eslint-plugin-zod": "4.14.2",
     "oxfmt": "0.70.0",
     "oxlint": "1.85.0",
-    "oxlint-tsgolint": "7.0.2002",
+    "oxlint-tsgolint": "7.0.2003",
     "sonda": "0.14.0",
     "tsdown": "0.23.0",
     "typescript": "6.0.3",

package/dist/application-BE4vehXW.mjs

@@ -1 +0,0 @@
-import{n as e,t}from"./application-BzO9ywXQ.mjs";export{t as defineApplication,e as generatePluginFilesIfNeeded};