Skip to content

chore(deps): update dependency @tailor-platform/sdk to v2.41.0 - #233

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailor-platform-sdk-and-erp-kit-packages
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailor-platform-sdk-and-erp-kit-packages

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@tailor-platform/sdk (source) 2.40.0 → 2.41.0 age confidence

Release Notes

tailor-platform/sdk (@​tailor-platform/sdk)

v2.41.0

Compare Source

Minor Changes
  • #​2968 769eb5f Thanks @​toiroakr! - Import getDB from @tailor-platform/sdk/plugin/kysely-type/db and set contentMapper: true in kyselyTypePlugin instead of distPath to use Kysely types without running tailor generate or keeping a generated file. With TypeScript 7.1 or later and the SDK enabled as a content mapper for .tailor files in tsconfig.json, TypeScript derives the types from your TailorDB definitions and the plugin options. The plugin's temporal option applies to this getDB in deployed code, tailor function run, and tests run with tailorRuntime({ config }). tailor function script imports getDB from the SDK when the plugin sets contentMapper: true. DEFAULT_KYSELY_TYPES_DIST_PATH from @tailor-platform/sdk/plugin/kysely-type is deprecated because the SDK no longer uses it; set contentMapper: true instead of distPath. kyselyTypePlugin now requires one of distPath or contentMapper: true, and rejects both together.

  • #​3046 7556041 Thanks @​toiroakr! - tailor deploy -c a,b now resolves an idpUser trigger's idp to an IdP owned by another config in the same run, so the subscribing config no longer needs to declare that IdP with external: true in defineConfig({ idp }). The idpUser triggers also accept external: true next to idp to name an IdP the config does not declare without a type error. Triggers that omit idp and single-config deploys behave as before.

  • #​3086 c403d49 Thanks @​dqn! - Breaking change: The SDK no longer reads the old environment variable names that printed a deprecation warning. Rename them to the new names:

    • TAILOR_PLATFORM_SDK_CONFIG_PATH → TAILOR_CONFIG_PATH. With only the old name set, tailor deploy and deploy() use the default config file.
    • TAILOR_TOKEN → TAILOR_PLATFORM_TOKEN. With only the old name set, commands use the token of the profile or the logged-in user.
    • PLATFORM_URL → TAILOR_PLATFORM_URL and PLATFORM_OAUTH2_CLIENT_ID → TAILOR_PLATFORM_OAUTH2_CLIENT_ID. With only the old names set, commands use the profile's settings or the defaults.

    Workflows for several app directories that tailor setup generated with @tailor-platform/sdk-plugin-setup older than 0.15.0 set TAILOR_PLATFORM_SDK_CONFIG_PATH; update @tailor-platform/sdk-plugin-setup to 0.15.0 or later, then regenerate them with tailor setup update.

  • #​3041 8f01452 Thanks @​toiroakr! - Skip re-uploading unchanged function scripts on deploy after an SDK upgrade; only the sdk-version label is refreshed, and the plan summary shows how many function labels are refreshed

  • #​3080 e1f1410 Thanks @​toiroakr! - defineConfig() now takes idp as a single IdP, idp: myIdp, or as a single external declaration, idp: { name: "shared-idp", external: true }. The array form, idp: [myIdp], still works but is deprecated, which editors and no-deprecated lint rules show on the defineConfig() call, and will be removed in v3, where a config declares one IdP.

    tailor upgrade runs the v3/idp-array-to-single codemod, which writes the IdP of a one-element array as the idp value itself and removes an empty array. An array with two or more IdPs has no mechanical replacement, so the codemod reports it for you to change by hand.

    export default defineConfig({
      name: "backoffice",
      idp: backofficeIdp,
    });
  • #​3081 9f4d33d Thanks @​dqn! - Use uppercase, descriptive query error codes: invalid_sql → INVALID_SQL, invalid_namespace → QUERY_SCHEMA_LOAD_FAILED, and not_found → MACHINE_USER_NOT_FOUND. Update scripts that compare these codes to use the new values.

  • #​3073 b3bcbe2 Thanks @​dqn! - Expose PluginValidationError for structured plugin configuration failures. Report all duplicate frontend site names and argument indices with FRONTEND_SITE_DUPLICATE instead of UNEXPECTED_ERROR.

  • #​3013 75a6b2b Thanks @​toiroakr! - The seed schema files tailor generate writes now import defineSchema (and fillIdpUserPassword for the IdP user) from @tailor-platform/sdk-plugin-seed/schema instead of @tailor-platform/sdk/seed. Update @tailor-platform/sdk-plugin-seed to the release that adds the ./schema entry (install it first if the project does not have it; the tailor seed commands need it as well), then run tailor generate again to rewrite the files. With an older plugin, tailor seed validate cannot load the regenerated files and tsc reports TS2307 for @tailor-platform/sdk-plugin-seed/schema. The v3/seed-subpath-to-plugin codemod entry tells tailor upgrade to re-run tailor generate. Schema files generated before keep working. @tailor-platform/sdk/seed is now @deprecated and is removed in v3: import defineSchema, fillIdpUserPassword, ForeignKeyDefinition, and IndexDefinition from @tailor-platform/sdk-plugin-seed/schema instead. validateSeedData, fillSeedData, and hookSeedRows have no replacement import; run tailor seed validate, tailor seed fill, or tailor seed apply.

  • #​3005 5c1d974 Thanks @​toiroakr! - tailor executor trigger --header and triggerExecutor now deliver headers to an incoming-webhook executor as its headers. Before, the values were not passed on and the executor received empty headers, and the command warned when --header was given; the warning is gone. --header lower-cases header names: a header given once reaches the executor as a string, and a header given more than once (names that differ only in letter case are the same header) as an array of strings, as when a request sends it on more than one line. triggerExecutor takes a headers option for incoming-webhook executors, and a type error rejects it for other executors. It sends each name as given, with a string or an array of strings as the value, and rejects two keys that differ only in letter case. A manual trigger still delivers no rawBody, so test an executor that verifies a signature over rawBody through its webhook URL.

  • #​3068 fcc4514 Thanks @​dqn! - Preserve optional nested properties in Kysely select types to match results where omitted keys are absent. Code reading these properties must handle both null and undefined, for example with bio != null before accessing bio.length.

    Generated Kysely types now use plain objects and arrays for nested fields whose only special property is optionality, preserving their select, insert, and update types.

Patch Changes
  • #​3063 6759ec1 Thanks @​dqn! - Report invalid configuration with CONFIG_INVALID issue paths and list every duplicate TailorDB table name with its definition sources.

  • #​3052 9a57860 Thanks @​dqn! - Document how to suppress intentional workflow drift findings with the ignore input of the generated tailor-drift-check step

  • #​2968 32f251e Thanks @​toiroakr! - Open a project in the editor with less work when the SDK is enabled as a content mapper: it no longer bundles the hooks and validators of your TailorDB tables just to type db.tailor. tailor deploy and tailor generate are unchanged.

  • #​3071 a7b38e8 Thanks @​dqn! - Fix getGeneratedTable and getExtendedTable to honor default test-file exclusions, explicit ignores, and ordered negations when resolving table namespaces

  • #​3043 34d46ca Thanks @​dqn! - A credential detected in env of defineConfig is now reported as an invalid config rather than an unexpected error. In --json output the error has code: "CONFIG_INVALID" instead of UNEXPECTED_ERROR, lists each offending key under context.issues (path: ["env", "<KEY>"]), and carries the fix, moving the value to Secret Manager or allowing it with allowSecretReason, in suggestion and the reason in details instead of in message. Plain output prints the same parts as Error [CONFIG_INVALID]: tailor.config.ts: Invalid Tailor config: followed by the issue list and Details: and Suggestion: lines. When loadConfig from @tailor-platform/sdk/cli throws this error, its error.message holds only the Invalid Tailor config: heading and the issue list.

  • #​3050 db7bbc7 Thanks @​dqn! - A MIGRATION_FAILED error from tailor deploy now names the migration whose script failed: its message starts with Migration <namespace>/<number> failed, and error.context carries namespace and migrationNumber. Under --json the error used to carry only the script's own message, so a deploy with several pending migrations did not say which one failed.

  • #​3045 c21f351 Thanks @​dqn! - tailor deploy, tailor tailordb migration sync, and tailor tailordb migration resolve now report a table update that is refused because records have no value for a newly required field with the error code TAILORDB_REQUIRED_FIELD_HAS_NULL_VALUES and the remediation in error.suggestion. Under --json the error used to carry only RPC_FAILED_PRECONDITION, with the remediation printed as text on stderr; human output now shows it on the error's Suggestion: line, and code that calls deploy() reads it with errorToJson() instead of from stderr. When no migration covers the change, tailor deploy now suggests filling in the missing values and deploying again, and suggests tailor tailordb migration generate, with the deploy's --config, only for a namespace with migration configured. A migration that stays in progress because its in-progress record could not be cleared keeps the remediation of the failure that stopped it.

  • #​3061 4d7c95e Thanks @​k1LoW! - tailor deploy now fetches the full definition of each existing executor it plans to keep, and compares the local executor against that instead of the executor list. Deploy plans stay the same, and the comparison keeps working when the platform stops returning target configurations in the executor list.

  • #​3064 c6d733f Thanks @​dqn! - Preserve specific error codes through HTTP adapter and workflow bundle hooks, and report unsupported handlers, validators and unresolved workflow dependencies with structured diagnostics.

    Document that field-level and table-level validators must be synchronous.

  • #​3053 e54ec31 Thanks @​dqn! - Report every pre-flight validation failure of tailor deploy at once: violations from all configs in the run are listed together, and the DEPLOY_VALIDATION_FAILED error carries them in error.context.issues under --json.

    Warnings for requests that could not be validated now identify their application.

  • #​3051 2cbad91 Thanks @​dqn! - A tailor.config.ts with no default export, a plugins export that is not an array, or two plugins sharing an id is now reported as an invalid config rather than an unexpected error. In --json output the error has code: "CONFIG_INVALID" instead of UNEXPECTED_ERROR and carries context.file, context.exportName and context.issues; the missing default export and the duplicate ID also carry a suggestion. Plain output prints Error [CONFIG_INVALID]: tailor.config.ts: Invalid Tailor config: or Invalid `plugins` export: followed by the issue list, and error.message of the error loadConfig from @tailor-platform/sdk/cli throws changes to that heading and list. Every rejected item of the plugins export is now listed in one error instead of only the first.

  • #​3069 dc086aa Thanks @​dqn! - Report invalid TailorDB table names with the definition file and export name before deployment.

  • #​3074 1a10a71 Thanks @​dqn! - Preserve original source locations in workflow and function error stack traces after bundling.

  • #​3042 52bd46a Thanks @​dqn! - The platform now rejects creating or updating an IdP whose allowedEmailDomains is empty or omitted unless useNonEmailIdentifier is true, so tailor deploy fails on such an IdP. That includes an IdP deployed earlier, on the first deploy after upgrading the SDK, which updates every IdP. Add allowedEmailDomains: ["*"] to the IdP's userAuthPolicy (adding userAuthPolicy when the IdP has none) to keep allowing every email domain, or list the domains you accept. Newly scaffolded executor, generators, and static-web-site projects now set ["*"], the deploy warning about an empty list now says the platform rejects it, and the IdP docs describe the requirement.

  • #​3047 8dc7126 Thanks @​dqn! - Type the optional fields and tables a migration adds in its generated db.ts, so migrate.ts can query them. A field the migration makes optional is now typed as nullable there, as in db.pglite.ts.

  • #​3049 763c0bd Thanks @​dqn! - Fix the event publishing example in the resolver docs to pass the resolver definition to resolverExecutedTrigger instead of its name

  • #​3016 cd01a32 Thanks @​dqn! - Add the no-unused-resolver-input lint rule, which reports a resolver input field that body never reads, since a caller may expect it to take effect. A field that permission compares with the caller or that declares a validate counts as used, and a resolver whose body passes its input on in a way that hides which fields it reads is not reported. Silence a field kept on purpose with eslint-disable-next-line. Enabled in the ESLint recommended config and in newly scaffolded projects; existing Oxlint projects add "tailor-sdk/no-unused-resolver-input": "warn" to .oxlintrc.json.

  • #​3067 449f79f Thanks @​dqn! - Preserve source file and line information in function run --watch error output.

  • #​2949 930cb91 Thanks @​toiroakr! - Reduce CLI and config-loader startup time: relative times such as "5 minutes ago" no longer load date-fns at startup, TailorDBField.clone() no longer loads es-toolkit, and date-fns is no longer installed with the SDK

  • #​2930 5ab35c2 Thanks @​renovate! - fix(deps): update rolldown

  • #​3004 6852128 Thanks @​renovate! - fix(deps): update dependency @​​politty/zod to v0.7.2

  • #​3034 96e501b Thanks @​renovate! - fix(deps): update dependency es-toolkit to v1.53.2

  • #​2930 5ab35c2 Thanks @​renovate! - fix(deps): update @​​opentelemetry

  • #​3038 a6f3c9d Thanks @​renovate! - fix(deps): update dependency @​​bufbuild/protobuf to v2.17.0

  • #​3039 92d5412 Thanks @​renovate! - fix(deps): update dependency lines-db to v0.19.0

  • #​3072 6f7c703 Thanks @​dqn! - Fix indentation of multiline function logs in normal, follow, and workflow execution views

  • #​3070 d3aa423 Thanks @​dqn! - Validate machine users for migration tests before creating or modifying the target workspace, with the same diagnostics as deploy. Reject empty --machine-user overrides and preserve seed plugin precedence.

  • #​3054 eead6d8 Thanks @​dqn! - Report three config and definition mistakes with their own error codes instead of UNEXPECTED_ERROR, so --json output carries the facts in context:

    • An invalid resolver defaultPermission is CONFIG_INVALID. The error is located at the config file and lists each issue with its path, such as resolver.main.defaultPermission.0.conditions.0.0.
    • tailor function run on a resolver file that more than one resolver namespace's files match is RESOLVER_NAMESPACE_AMBIGUOUS, located at the config file, with the namespaces in context and the remedy in suggestion.
    • Resolvers in one namespace, executors, workflow jobs, HTTP adapters, IdPs, static websites, or AI Gateways that share a name are DEFINITION_NAME_DUPLICATE. The error lists every definition of every duplicated name rather than the first pair, carries the remedy in suggestion, and prints workflow job and HTTP adapter files relative to the current directory.

    For duplicate IdPs, static websites, and AI Gateways, each definition includes its config file and array path in context, so entries in the same config can be distinguished.

  • #​3015 0d690dc Thanks @​dqn! - Add the no-unbound-caller-id-input lint rule, which reports a resolver mutation's t.uuid() or db.uuid() input named like the caller's ID, such as approverId, requesterId, or createdBy, unless every permit: true policy of its permission compares the input with the caller; otherwise a caller can act as another user by sending that user's ID. Enabled in newly scaffolded projects and in the ESLint recommended config; add "tailor-sdk/no-unbound-caller-id-input": "warn" to the rules of an existing .oxlintrc.json to enable it there.

  • #​3056 db0572a Thanks @​dqn! - Report CLI workspace, credential, query and shared utility failures with specific error codes, recovery suggestions and structured context.

    Include the editor command in the error message when the editor exits with a failure.

  • #​3040 23c2e7c Thanks @​dqn! - Consolidate shared CLI and seed handling while preserving existing command behavior.

  • #​2990 dd9d551 Thanks @​dqn! - tailor generate, tailor deploy, and other commands that load TailorDB types, resolvers, executors, workflows, and HTTP adapters now print a loading failure once instead of two or three times. When several files fail to load at once, the files other than the reported one are listed by name without their errors.

    An error that points at tailor.config.ts or at a TailorDB type, resolver, executor, workflow, or HTTP adapter file, such as a syntax or definition error, an invalid config, or any failure while loading one of those files, now starts with the file's path and, when known, the line, both in plain output and in the --json message: tailordb/order.ts:3: Invalid syntax: Expression expected instead of Invalid syntax in tailordb/order.ts:3: Expression expected. When generate, deploy, or loadConfig from @tailor-platform/sdk/cli throws one of these errors, its error.message no longer names the file; errorToJson(error).error.message does. An error marked with withSourceLocation is printed the same way unless it is an error of your own with a format() that returns a string.

  • #​3044 7394ef2 Thanks @​dqn! - tailor query --engine sql now writes the row count of its text output to stderr as ℹ rows: N, in the REPL too, instead of rows: N on stdout, so piping the output captures only the result tables. --json output is unchanged; a script that needs the count can read rowCount there.

  • #​3048 a0179ce Thanks @​dqn! - tailor deploy now fails before it applies any change when it would create or update an IdP whose allowedEmailDomains is empty or omitted and useNonEmailIdentifier is not true, and tailor deploy --dry-run fails on such a plan too. Deploy used to create or update the secrets, static websites, and AI gateways in the same run first and then fail on the IdP, which it still does with --no-validate.

  • #​3005 5c1d974 Thanks @​toiroakr! - Type the headers that RFC 9110 defines as comma-separated lists, such as accept and via, and x-forwarded-for as string | string[] in args.headers of an incoming-webhook executor when incomingWebhookTrigger has no type argument. A header sent on more than one line arrives as an array, so the type now matches the values the Platform delivers. Any other header stays a string, and args.headers can still be passed to a parameter typed Record<string, string>. The type argument of incomingWebhookTrigger now takes only what you want to override: body replaces the body type, each header named in headers replaces the type of that header, and everything not named keeps its default, except that when a named header is an array, the headers that are not named may also be arrays. Behavior is unchanged. Code that passes one of these list headers to a parameter typed string now fails type checking; narrow it with Array.isArray first, or name that header as string in the type argument.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner November 16, 2026 05:09
@renovate
renovate Bot force-pushed the renovate/tailor-platform-sdk-and-erp-kit-packages branch from 0fbf038 to d2fbdfe Compare November 16, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants