Repository navigation
chore(deps): update dependency @tailor-platform/sdk to v2.41.0 - #233
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/tailor-platform-sdk-and-erp-kit-packages
branch
from
November 16, 2026 18:48
0fbf038 to
d2fbdfe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.40.0→2.41.0Release Notes
tailor-platform/sdk (@tailor-platform/sdk)
v2.41.0Compare Source
Minor Changes
#2968
769eb5fThanks @toiroakr! - ImportgetDBfrom@tailor-platform/sdk/plugin/kysely-type/dband setcontentMapper: trueinkyselyTypePlugininstead ofdistPathto use Kysely types without runningtailor generateor keeping a generated file. With TypeScript 7.1 or later and the SDK enabled as a content mapper for.tailorfiles in tsconfig.json, TypeScript derives the types from your TailorDB definitions and the plugin options. The plugin'stemporaloption applies to thisgetDBin deployed code,tailor function run, and tests run withtailorRuntime({ config }).tailor function scriptimportsgetDBfrom the SDK when the plugin setscontentMapper: true.DEFAULT_KYSELY_TYPES_DIST_PATHfrom@tailor-platform/sdk/plugin/kysely-typeis deprecated because the SDK no longer uses it; setcontentMapper: trueinstead ofdistPath.kyselyTypePluginnow requires one ofdistPathorcontentMapper: true, and rejects both together.#3046
7556041Thanks @toiroakr! -tailor deploy -c a,bnow resolves anidpUsertrigger'sidpto an IdP owned by another config in the same run, so the subscribing config no longer needs to declare that IdP withexternal: trueindefineConfig({ idp }). TheidpUsertriggers also acceptexternal: truenext toidpto name an IdP the config does not declare without a type error. Triggers that omitidpand single-config deploys behave as before.#3086
c403d49Thanks @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 deployanddeploy()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_URLandPLATFORM_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 setupgenerated with@tailor-platform/sdk-plugin-setupolder than 0.15.0 setTAILOR_PLATFORM_SDK_CONFIG_PATH; update@tailor-platform/sdk-plugin-setupto 0.15.0 or later, then regenerate them withtailor setup update.#3041
8f01452Thanks @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
e1f1410Thanks @toiroakr! -defineConfig()now takesidpas 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 andno-deprecatedlint rules show on thedefineConfig()call, and will be removed in v3, where a config declares one IdP.tailor upgraderuns thev3/idp-array-to-singlecodemod, which writes the IdP of a one-element array as theidpvalue 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.#3081
9f4d33dThanks @dqn! - Use uppercase, descriptive query error codes:invalid_sql→INVALID_SQL,invalid_namespace→QUERY_SCHEMA_LOAD_FAILED, andnot_found→MACHINE_USER_NOT_FOUND. Update scripts that compare these codes to use the new values.#3073
b3bcbe2Thanks @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
75a6b2bThanks @toiroakr! - The seed schema filestailor generatewrites now importdefineSchema(andfillIdpUserPasswordfor the IdP user) from@tailor-platform/sdk-plugin-seed/schemainstead of@tailor-platform/sdk/seed. Update@tailor-platform/sdk-plugin-seedto the release that adds the./schemaentry (install it first if the project does not have it; thetailor seedcommands need it as well), then runtailor generateagain to rewrite the files. With an older plugin,tailor seed validatecannot load the regenerated files andtscreports TS2307 for@tailor-platform/sdk-plugin-seed/schema. Thev3/seed-subpath-to-plugincodemod entry tellstailor upgradeto re-runtailor generate. Schema files generated before keep working.@tailor-platform/sdk/seedis now@deprecatedand is removed in v3: importdefineSchema,fillIdpUserPassword,ForeignKeyDefinition, andIndexDefinitionfrom@tailor-platform/sdk-plugin-seed/schemainstead.validateSeedData,fillSeedData, andhookSeedRowshave no replacement import; runtailor seed validate,tailor seed fill, ortailor seed apply.#3005
5c1d974Thanks @toiroakr! -tailor executor trigger --headerandtriggerExecutornow deliver headers to an incoming-webhook executor as itsheaders. Before, the values were not passed on and the executor received emptyheaders, and the command warned when--headerwas given; the warning is gone.--headerlower-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.triggerExecutortakes aheadersoption 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 norawBody, so test an executor that verifies a signature overrawBodythrough its webhook URL.#3068
fcc4514Thanks @dqn! - Preserve optional nested properties in Kysely select types to match results where omitted keys are absent. Code reading these properties must handle bothnullandundefined, for example withbio != nullbefore accessingbio.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
6759ec1Thanks @dqn! - Report invalid configuration with CONFIG_INVALID issue paths and list every duplicate TailorDB table name with its definition sources.#3052
9a57860Thanks @dqn! - Document how to suppress intentional workflow drift findings with theignoreinput of the generatedtailor-drift-checkstep#2968
32f251eThanks @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 typedb.tailor.tailor deployandtailor generateare unchanged.#3071
a7b38e8Thanks @dqn! - Fix getGeneratedTable and getExtendedTable to honor default test-file exclusions, explicit ignores, and ordered negations when resolving table namespaces#3043
34d46caThanks @dqn! - A credential detected inenvofdefineConfigis now reported as an invalid config rather than an unexpected error. In--jsonoutput the error hascode: "CONFIG_INVALID"instead ofUNEXPECTED_ERROR, lists each offending key undercontext.issues(path: ["env", "<KEY>"]), and carries the fix, moving the value to Secret Manager or allowing it withallowSecretReason, insuggestionand the reason indetailsinstead of inmessage. Plain output prints the same parts asError [CONFIG_INVALID]: tailor.config.ts: Invalid Tailor config:followed by the issue list andDetails:andSuggestion:lines. WhenloadConfigfrom@tailor-platform/sdk/clithrows this error, itserror.messageholds only theInvalid Tailor config:heading and the issue list.#3050
db7bbc7Thanks @dqn! - AMIGRATION_FAILEDerror fromtailor deploynow names the migration whose script failed: its message starts withMigration <namespace>/<number> failed, anderror.contextcarriesnamespaceandmigrationNumber. Under--jsonthe error used to carry only the script's own message, so a deploy with several pending migrations did not say which one failed.#3045
c21f351Thanks @dqn! -tailor deploy,tailor tailordb migration sync, andtailor tailordb migration resolvenow report a table update that is refused because records have no value for a newly required field with the error codeTAILORDB_REQUIRED_FIELD_HAS_NULL_VALUESand the remediation inerror.suggestion. Under--jsonthe error used to carry onlyRPC_FAILED_PRECONDITION, with the remediation printed as text on stderr; human output now shows it on the error'sSuggestion:line, and code that callsdeploy()reads it witherrorToJson()instead of from stderr. When no migration covers the change,tailor deploynow suggests filling in the missing values and deploying again, and suggeststailor tailordb migration generate, with the deploy's--config, only for a namespace withmigrationconfigured. 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
4d7c95eThanks @k1LoW! -tailor deploynow 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
c6d733fThanks @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
e54ec31Thanks @dqn! - Report every pre-flight validation failure oftailor deployat once: violations from all configs in the run are listed together, and theDEPLOY_VALIDATION_FAILEDerror carries them inerror.context.issuesunder--json.Warnings for requests that could not be validated now identify their application.
#3051
2cbad91Thanks @dqn! - Atailor.config.tswith no default export, apluginsexport that is not an array, or two plugins sharing anidis now reported as an invalid config rather than an unexpected error. In--jsonoutput the error hascode: "CONFIG_INVALID"instead ofUNEXPECTED_ERRORand carriescontext.file,context.exportNameandcontext.issues; the missing default export and the duplicate ID also carry asuggestion. Plain output printsError [CONFIG_INVALID]: tailor.config.ts: Invalid Tailor config:orInvalid `plugins` export:followed by the issue list, anderror.messageof the errorloadConfigfrom@tailor-platform/sdk/clithrows changes to that heading and list. Every rejected item of thepluginsexport is now listed in one error instead of only the first.#3069
dc086aaThanks @dqn! - Report invalid TailorDB table names with the definition file and export name before deployment.#3074
1a10a71Thanks @dqn! - Preserve original source locations in workflow and function error stack traces after bundling.#3042
52bd46aThanks @dqn! - The platform now rejects creating or updating an IdP whoseallowedEmailDomainsis empty or omitted unlessuseNonEmailIdentifieristrue, sotailor deployfails on such an IdP. That includes an IdP deployed earlier, on the first deploy after upgrading the SDK, which updates every IdP. AddallowedEmailDomains: ["*"]to the IdP'suserAuthPolicy(addinguserAuthPolicywhen the IdP has none) to keep allowing every email domain, or list the domains you accept. Newly scaffoldedexecutor,generators, andstatic-web-siteprojects now set["*"], the deploy warning about an empty list now says the platform rejects it, and the IdP docs describe the requirement.#3047
8dc7126Thanks @dqn! - Type the optional fields and tables a migration adds in its generateddb.ts, somigrate.tscan query them. A field the migration makes optional is now typed as nullable there, as indb.pglite.ts.#3049
763c0bdThanks @dqn! - Fix the event publishing example in the resolver docs to pass the resolver definition toresolverExecutedTriggerinstead of its name#3016
cd01a32Thanks @dqn! - Add theno-unused-resolver-inputlint rule, which reports a resolverinputfield thatbodynever reads, since a caller may expect it to take effect. A field thatpermissioncompares with the caller or that declares avalidatecounts as used, and a resolver whosebodypasses its input on in a way that hides which fields it reads is not reported. Silence a field kept on purpose witheslint-disable-next-line. Enabled in the ESLintrecommendedconfig and in newly scaffolded projects; existing Oxlint projects add"tailor-sdk/no-unused-resolver-input": "warn"to.oxlintrc.json.#3067
449f79fThanks @dqn! - Preserve source file and line information in function run --watch error output.#2949
930cb91Thanks @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
5ab35c2Thanks @renovate! - fix(deps): update rolldown#3004
6852128Thanks @renovate! - fix(deps): update dependency @politty/zod to v0.7.2#3034
96e501bThanks @renovate! - fix(deps): update dependency es-toolkit to v1.53.2#2930
5ab35c2Thanks @renovate! - fix(deps): update @opentelemetry#3038
a6f3c9dThanks @renovate! - fix(deps): update dependency @bufbuild/protobuf to v2.17.0#3039
92d5412Thanks @renovate! - fix(deps): update dependency lines-db to v0.19.0#3072
6f7c703Thanks @dqn! - Fix indentation of multiline function logs in normal, follow, and workflow execution views#3070
d3aa423Thanks @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
eead6d8Thanks @dqn! - Report three config and definition mistakes with their own error codes instead ofUNEXPECTED_ERROR, so--jsonoutput carries the facts incontext:defaultPermissionisCONFIG_INVALID. The error is located at the config file and lists each issue with its path, such asresolver.main.defaultPermission.0.conditions.0.0.tailor function runon a resolver file that more than one resolver namespace'sfilesmatch isRESOLVER_NAMESPACE_AMBIGUOUS, located at the config file, with the namespaces incontextand the remedy insuggestion.DEFINITION_NAME_DUPLICATE. The error lists every definition of every duplicated name rather than the first pair, carries the remedy insuggestion, 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
0d690dcThanks @dqn! - Add theno-unbound-caller-id-inputlint rule, which reports a resolver mutation'st.uuid()ordb.uuid()input named like the caller's ID, such asapproverId,requesterId, orcreatedBy, unless everypermit: truepolicy of itspermissioncompares 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 ESLintrecommendedconfig; add"tailor-sdk/no-unbound-caller-id-input": "warn"to therulesof an existing.oxlintrc.jsonto enable it there.#3056
db0572aThanks @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
23c2e7cThanks @dqn! - Consolidate shared CLI and seed handling while preserving existing command behavior.#2990
dd9d551Thanks @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.tsor 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--jsonmessage:tailordb/order.ts:3: Invalid syntax: Expression expectedinstead ofInvalid syntax in tailordb/order.ts:3: Expression expected. Whengenerate,deploy, orloadConfigfrom@tailor-platform/sdk/clithrows one of these errors, itserror.messageno longer names the file;errorToJson(error).error.messagedoes. An error marked withwithSourceLocationis printed the same way unless it is an error of your own with aformat()that returns a string.#3044
7394ef2Thanks @dqn! -tailor query --engine sqlnow writes the row count of its text output to stderr asℹ rows: N, in the REPL too, instead ofrows: Non stdout, so piping the output captures only the result tables.--jsonoutput is unchanged; a script that needs the count can readrowCountthere.#3048
a0179ceThanks @dqn! -tailor deploynow fails before it applies any change when it would create or update an IdP whoseallowedEmailDomainsis empty or omitted anduseNonEmailIdentifieris nottrue, andtailor deploy --dry-runfails 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
5c1d974Thanks @toiroakr! - Type the headers that RFC 9110 defines as comma-separated lists, such asacceptandvia, andx-forwarded-forasstring | string[]inargs.headersof an incoming-webhook executor whenincomingWebhookTriggerhas 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, andargs.headerscan still be passed to a parameter typedRecord<string, string>. The type argument ofincomingWebhookTriggernow takes only what you want to override:bodyreplaces the body type, each header named inheadersreplaces 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 typedstringnow fails type checking; narrow it withArray.isArrayfirst, or name that header asstringin the type argument.Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.