@tailor-platform/sdk 2.21.0 → 2.23.0

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # @tailor-platform/sdk
 
+## 2.23.0
+
+### Minor Changes
+
+- [#2440](https://github.com/tailor-platform/sdk/pull/2440) [`e2df6cf`](https://github.com/tailor-platform/sdk/commit/e2df6cfa8acd4acf1cbd46418855aa93127b70d3) Thanks [@dqn](https://github.com/dqn)! - `tailor deploy` now marks updates that show no configuration difference and are applied again only because the application's resources were last deployed with a different SDK version. The plan lists them with `[forced by SDK version]` and the summary counts them (`12 to update (11 forced by SDK version)`), so after an SDK upgrade you can tell them apart from real configuration changes. With `--json`, such changes carry `forcedBySdkVersion: true` and `summary.forcedBySdkVersion` counts them.
+
+### Patch Changes
+
+- [#2442](https://github.com/tailor-platform/sdk/pull/2442) [`4a974b1`](https://github.com/tailor-platform/sdk/commit/4a974b1a16a5e2b9ff9e1e130962053b055a96af) Thanks [@dqn](https://github.com/dqn)! - Fix the `tailor deploy` plan leaving out workflow execution policies: their changes are now listed in the Workflow section, and unmanaged or conflicting execution policies and applications now appear in the plan's warnings and owner conflicts, including `--json` output.
+
+- [#2462](https://github.com/tailor-platform/sdk/pull/2462) [`551179a`](https://github.com/tailor-platform/sdk/commit/551179ac9b0b44c3bfc46eca44b2507cad7c1511) Thanks [@k1LoW](https://github.com/k1LoW)! - Function execution logs are now read from the platform's structured log entries instead of the deprecated flat `logs` field. The `logs` string that `function run`, `function logs --json`, `workflow executions --logs`, `executor jobs --logs`, TailorDB migrations, and `executeScript()` return joins the messages of those entries with newlines, and `function logs` no longer falls back to the flat string when an execution has no structured entries.
+
+- [#2448](https://github.com/tailor-platform/sdk/pull/2448) [`317ba1e`](https://github.com/tailor-platform/sdk/commit/317ba1eb287ad650ae59b16e000911da484edf47) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency rolldown to v1.2.11
+
+- [#2438](https://github.com/tailor-platform/sdk/pull/2438) [`feb8b23`](https://github.com/tailor-platform/sdk/commit/feb8b2365c202a732be2d552dcb4a5d841101e2d) Thanks [@dqn](https://github.com/dqn)! - On Windows, a suggested follow-up command whose arguments cmd.exe and PowerShell read differently (for example a profile named `dev$1`, a config path containing `%`, or the webhook trigger's JSON body) is now shown as one command to copy into PowerShell and one to copy into cmd.exe, instead of an `argv [...]` array or a double-quoted line that PowerShell misreads. The `tailor profile update` suggestions shown for a read-only profile or a denied machine-user override now quote the profile name instead of pasting it into the command unquoted. On every platform, these suggested follow-up commands are now set off in backticks.
+
+- [#2462](https://github.com/tailor-platform/sdk/pull/2462) [`0dcbed6`](https://github.com/tailor-platform/sdk/commit/0dcbed6f3c4f1847e8864febb1c43d0d00fdffae) Thanks [@k1LoW](https://github.com/k1LoW)! - Workflow commands now recognize canceled workflow executions. `workflow start --wait`, `workflow wait`, `workflow executions <id> --wait`, and `executor jobs --wait` over a workflow stop at a canceled execution and fail with `WORKFLOW_EXECUTION_CANCELED` instead of polling until they time out, a TailorDB migration whose workflow is canceled fails instead of waiting indefinitely, the status is shown as `CANCELED` rather than `UNSPECIFIED`, and `workflow executions --status CANCELED` is accepted.
+
+## 2.22.0
+
+### Minor Changes
+
+- [#2346](https://github.com/tailor-platform/sdk/pull/2346) [`87a6579`](https://github.com/tailor-platform/sdk/commit/87a65793bb8d8c6d5335f69d672db4ce4bc6ab9c) Thanks [@dqn](https://github.com/dqn)! - Add the `TAILOR_JSON_OUTPUT` environment variable to default CLI output to JSON without passing `--json` on every call, for agents, scripts, and CI. Set it to `true` or `1` to enable JSON; `false` or `0` keeps table output. An explicit `--json` still wins, and with the variable unset every command keeps its current output, so existing pipes and CI steps are unaffected. Dispatched CLI plugins inherit the variable from the environment.
+
+- [#2403](https://github.com/tailor-platform/sdk/pull/2403) [`7c3e1cc`](https://github.com/tailor-platform/sdk/commit/7c3e1cc540230173e3f699085019879781bd309e) Thanks [@toiroakr](https://github.com/toiroakr)! - `@tailor-platform/sdk/cli` now exports `appIdLockKey` and `resolveAppId`, so a CLI plugin can read a config's application id the same way `deploy` does — preferring the id recorded in `.github/tailor.lock`, falling back to the id the config module evaluates to. `resolveAppId` never writes the lock, edits the config, or prompts, and resolves to `undefined` without warning when neither source has an id. A config id that disagrees with the lock, or that already belongs to a different, still-existing config, throws `APP_ID_CONFLICT` instead of guessing.
+
+- [#2339](https://github.com/tailor-platform/sdk/pull/2339) [`1d60b6a`](https://github.com/tailor-platform/sdk/commit/1d60b6ab84089d4b645fbcc4b96fbceb59b3ce6f) Thanks [@toiroakr](https://github.com/toiroakr)! - Lock the beta plugin config export name to `plugins`. `definePlugins()` must be assigned to `export const plugins` in `tailor.config.ts`; any other export name (`plugins2`, `generator`, `generators`, etc.) is no longer read for plugins, matching the documented convention. A `plugins` export that is not an array, or that contains an item that is not a valid plugin, now fails config loading with a descriptive error instead of being silently dropped. A duplicate plugin ID within `plugins` now fails config loading in every code path instead of silently keeping only the last one.
+  
+  Provide a v2 minor-release upgrade codemod for existing `generator`/`generators` exports. Preserve unrelated imports and shadowed variables, and leave imports unchanged when their config cannot be safely renamed. Include `.mts` and `.cts` imports and report remaining split exports or multiple plugin arrays for manual migration.
+
+### Patch Changes
+
+- [#2428](https://github.com/tailor-platform/sdk/pull/2428) [`1f18ce8`](https://github.com/tailor-platform/sdk/commit/1f18ce802e65f2e49958696d9bd3ff09b50f8cbf) Thanks [@toiroakr](https://github.com/toiroakr)! - Fix `FORBIDDEN_RUNTIME_GLOBAL` wrongly rejecting workflow jobs and executors whose dependencies detect the environment with `typeof` ternaries such as `typeof global !== "undefined" ? global : ...` or `typeof window === "undefined" ? {} : window`, including after the bundle is minified
+  
+  Fix TailorDB hooks and validators dropping a constant from the same file when they read it behind a `typeof` check such as `typeof DEFAULT_VALUE !== "undefined" && DEFAULT_VALUE`
+
+- [#2426](https://github.com/tailor-platform/sdk/pull/2426) [`3ebdc0c`](https://github.com/tailor-platform/sdk/commit/3ebdc0ca1eac2c1c0f2c02d7eb2ce43dffe5a715) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency @​toiroakr/lines-db to v0.13.0
+
+- [#2429](https://github.com/tailor-platform/sdk/pull/2429) [`214e199`](https://github.com/tailor-platform/sdk/commit/214e199c48d4cfeecfaf1766186a9a2805cdbeb4) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency get-east-asian-width to v1.7.0
+
+- [#2430](https://github.com/tailor-platform/sdk/pull/2430) [`b6a0146`](https://github.com/tailor-platform/sdk/commit/b6a014646bc7ff8ca540cb1ae1ce5ce7efdd10ce) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update dependency type-fest to v5.10.0
+
+- [#2431](https://github.com/tailor-platform/sdk/pull/2431) [`716c337`](https://github.com/tailor-platform/sdk/commit/716c3373cfd30a1535a2396594f6a95d4f97e6c9) Thanks [@renovate](https://github.com/apps/renovate)! - fix(deps): update oxc
+
+- [#2444](https://github.com/tailor-platform/sdk/pull/2444) [`c4fcd01`](https://github.com/tailor-platform/sdk/commit/c4fcd01d68e7c266d2232fc89f7b6a9d58cc4f5f) Thanks [@renovate](https://github.com/apps/renovate)! - chore(deps): lock file maintenance
+
+- [#2426](https://github.com/tailor-platform/sdk/pull/2426) [`f3a0671`](https://github.com/tailor-platform/sdk/commit/f3a067173226f5eced1b24ca544a02da7607762f) Thanks [@renovate](https://github.com/apps/renovate)! - `tailor seed validate` now reports a JSONL line that is not valid JSON with its file and line, and points the GitHub Actions annotation at that line.
+
+- [#2419](https://github.com/tailor-platform/sdk/pull/2419) [`c984ba0`](https://github.com/tailor-platform/sdk/commit/c984ba08adb6effa9717645f7fe836be63476ff7) Thanks [@dqn](https://github.com/dqn)! - Re-running `tailor setup ci` now keeps your own jobs, steps, and top-level keys in generated workflows and composite actions, along with `runs-on` / `timeout-minutes` / `container` / `env` on managed jobs and the documented editable inputs (such as `user-mapping` on `tailor-notify`). `tailor setup check` only reports edits to SDK-managed parts, and `--force` resets those parts without discarding your additions. Files generated by an older version need one `--force` re-run if you had edited them.
+  
+  `setup ci branch`, `setup ci tag`, and `setup ci coordinate` accept `--restrict-dispatch`, which lets a manual `workflow_dispatch` deploy only the target branch (branch targets) or a tag, which must also pass the reachability guard when `--branch` is set (tag targets). Dry runs stay available from any ref.
+
 ## 2.21.0
 
 ### Minor Changes

package/agent-skills/tailor/SKILL.md

@@ -26,7 +26,9 @@ Use these files as the single source of truth:
 1. Prefer SDK docs above assumptions. If behavior is unclear, cite the exact doc path used.
 2. Keep examples compatible with Node.js 22+.
 3. For CLI questions, verify command and option names from `docs/cli-reference.md` and `docs/cli/*.md`.
-4. For configuration questions, validate examples against `docs/configuration.md` and related service docs.
+4. When running CLI commands, set `TAILOR_JSON_OUTPUT=true` (or pass `--json`) and parse the JSON
+   instead of the table output, which is formatted for humans and may change.
+5. For configuration questions, validate examples against `docs/configuration.md` and related service docs.
 
 ## Quick Navigation
 

package/dist/aigateway-DsWDjzk4.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"aigateway-DsWDjzk4.mjs","names":[],"sources":["../src/runtime/aigateway.ts"],"sourcesContent":["/**\n * AI Gateway utilities.\n *\n * Thin typed wrapper around the platform-provided `tailor.aigateway` runtime API.\n * At runtime this delegates to `globalThis.tailor.aigateway`. Use `mockAigateway`\n * from `@tailor-platform/sdk/vitest` to mock these calls in unit tests.\n *\n * `name` is narrowed to the AI Gateway names defined via `defineAIGateway()`\n * once `tailor.d.ts` has been generated (via `tailor deploy`/`generate`).\n * @example\n * import { aigateway } from \"@tailor-platform/sdk/runtime\";\n *\n * const { url } = await aigateway.get(\"my-aigateway\");\n */\n\n// Import from the public entry (not `#/configure/types/aigateway-name`) so this d.ts\n// references `@tailor-platform/sdk` externally instead of inlining the registry — the\n// same generated `declare module \"@tailor-platform/sdk\"` that narrows\n// `authconnection.getConnectionToken` then also narrows this entry.\nimport type { AIGatewayName } from \"@tailor-platform/sdk\";\n\n/** Result of {@link TailorAigatewayAPI.get}. */\nexport interface GetAIGatewayResult {\n  /** The platform-assigned URL of the AI Gateway. */\n  url: string;\n}\n\n/**\n * Platform API surface for `tailor.aigateway`. Describes the shape the\n * platform runtime injects on `globalThis.tailor.aigateway`.\n */\nexport interface TailorAigatewayAPI {\n  /**\n   * Resolves an AI Gateway defined in the caller's own workspace.\n   * @param name - AI Gateway name, as passed to `defineAIGateway()`\n   * @returns The resolved AI Gateway's platform-assigned URL\n   */\n  get(name: AIGatewayName): Promise<GetAIGatewayResult>;\n}\n\nconst api = (): TailorAigatewayAPI =>\n  (globalThis as unknown as { tailor: { aigateway: TailorAigatewayAPI } }).tailor.aigateway;\n\nconst get: TailorAigatewayAPI[\"get\"] = (...args) => api().get(...args);\n\n/** Runtime wrapper namespace for `tailor.aigateway`. */\nexport const aigateway = { get } as const satisfies TailorAigatewayAPI;\n"],"mappings":"AAwCA,MAAM,QACH,WAAwE,OAAO,UAKrE,EAAY,CAAE,KAHa,GAAG,IAAS,IAAI,CAAC,CAAC,IAAI,GAAG,CAAI,CAGtC"}
+{"version":3,"file":"aigateway-DsWDjzk4.mjs","names":["aigateway","args"],"sources":["../src/runtime/aigateway.ts"],"sourcesContent":["/**\n * AI Gateway utilities.\n *\n * Thin typed wrapper around the platform-provided `tailor.aigateway` runtime API.\n * At runtime this delegates to `globalThis.tailor.aigateway`. Use `mockAigateway`\n * from `@tailor-platform/sdk/vitest` to mock these calls in unit tests.\n *\n * `name` is narrowed to the AI Gateway names defined via `defineAIGateway()`\n * once `tailor.d.ts` has been generated (via `tailor deploy`/`generate`).\n * @example\n * import { aigateway } from \"@tailor-platform/sdk/runtime\";\n *\n * const { url } = await aigateway.get(\"my-aigateway\");\n */\n\n// Import from the public entry (not `#/configure/types/aigateway-name`) so this d.ts\n// references `@tailor-platform/sdk` externally instead of inlining the registry — the\n// same generated `declare module \"@tailor-platform/sdk\"` that narrows\n// `authconnection.getConnectionToken` then also narrows this entry.\nimport type { AIGatewayName } from \"@tailor-platform/sdk\";\n\n/** Result of {@link TailorAigatewayAPI.get}. */\nexport interface GetAIGatewayResult {\n  /** The platform-assigned URL of the AI Gateway. */\n  url: string;\n}\n\n/**\n * Platform API surface for `tailor.aigateway`. Describes the shape the\n * platform runtime injects on `globalThis.tailor.aigateway`.\n */\nexport interface TailorAigatewayAPI {\n  /**\n   * Resolves an AI Gateway defined in the caller's own workspace.\n   * @param name - AI Gateway name, as passed to `defineAIGateway()`\n   * @returns The resolved AI Gateway's platform-assigned URL\n   */\n  get(name: AIGatewayName): Promise<GetAIGatewayResult>;\n}\n\nconst api = (): TailorAigatewayAPI =>\n  (globalThis as unknown as { tailor: { aigateway: TailorAigatewayAPI } }).tailor.aigateway;\n\nconst get: TailorAigatewayAPI[\"get\"] = (...args) => api().get(...args);\n\n/** Runtime wrapper namespace for `tailor.aigateway`. */\nexport const aigateway = { get } as const satisfies TailorAigatewayAPI;\n"],"mappings":"AAwCA,MAAM,QACH,WAAwE,OAAO,UAKrEA,EAAY,CAAE,KAHa,GAAGC,IAAS,IAAI,CAAC,CAAC,IAAI,GAAGA,CAAI,CAGtC"}

package/dist/application-BtZ8hmx9.mjs

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