Repository navigation
chore(deps): update dependency @tailor-platform/sdk to v2.40.0 - #228
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/tailor-platform-sdk-and-erp-kit-packages
branch
from
November 13, 2026 05:55
63aec3f to
ebcbc1d
Compare
k1LoW
approved these changes
Nov 13, 2026
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.38.0→2.40.0Release Notes
tailor-platform/sdk (@tailor-platform/sdk)
v2.40.0Compare Source
Minor Changes
#2986
57fa11aThanks @dqn! -filesindb,resolver,executor,workflow, andhttpAdapternow treats a pattern starting with!as an exclusion: for each file, the lastfilespattern that matches it decides. Before, such a pattern matched nothing and excluded nothing, so a config that already lists!patterns now leaves those files out, and the next deploy removes the resources they defined. A file that severalfilespatterns match is now loaded once.ignoresis deprecated and will be removed in v3, together with the default exclusion of**/*.test.tsand**/*.spec.ts.tailor upgraderuns thev3/files-ignores-to-negationcodemod, which movesignoresintofilesas!patterns and adds"!**/*.test.ts"and"!**/*.spec.ts"to services withoutignores.#3025
ee30e41Thanks @dqn! - The plugin hookonNamespaceLoadedis renamed toonTailorDBNamespaceLoaded, which says that it runs once for each TailorDB namespace in the config (except external ones). Its context and output types are renamed toTailorDBNamespaceLoadedContextandTailorDBNamespacePluginOutput.onNamespaceLoaded,PluginNamespaceProcessContext, andNamespacePluginOutputare deprecated and will be removed in v3; plugins that use them keep working until then. A plugin that defines bothonNamespaceLoadedandonTailorDBNamespaceLoadedis rejected when the config loads.tailor upgraderuns thev3/tailordb-namespace-loaded-renamecodemod, which renames the hook and the two types.#3014
3af9d37Thanks @dqn! - A resolver'spermissioncan now compare an input with the caller through an{ input: "<field>" }operand, e.g.[{ input: "employeeId" }, "=", { user: "id" }], so a caller cannot act on another user's data by sending their ID. The operand names a top-level non-arrayt.string(),t.uuid(), ort.enum()input field, is compared with=, can only be used in apermit: truepolicy, and never matches when the input is omitted.defaultPermissioncannot use it.#3028
3093df4Thanks @dqn! - Add--watchtotailor function run: it runs the function again each time you save the function file, a project file it imports, or the argument file, without deploying, and prints each run as-->/<--lines tagged with the execution ID. Add--arg-fileto read the argument from a JSON file; without it,--watchcreates a temporary argument file and prints its path.--argis now validated before anything contacts the Platform, so invalid JSON fails even for a resolver without input.#2943
fd6655bThanks @toiroakr! - With TypeScript 7.1 or later, add the SDK as a content mapper for.tailorfiles in tsconfig.json and TypeScript readsEnv,Attributes,MachineUserName,IdpName, and the other names yourtailor.config.tsdefines directly from the config, so you no longer needtailor.d.ts. When thetsconfig.jsonthat applies totailor.config.tsenables the mapper,tailor generateandtailor deploystop writingtailor.d.tsand warn if an old copy remains.#3017
06e8d17Thanks @dqn! - Export theTailorAnyFieldtype so helpers that buildt.object()inputs or outputs can accept anyt.*ordb.*field and keep its type.#2991
5bc1ffdThanks @dqn! - Breaking change (beta):mockSecretmanagernow makesgetSecret()andgetSecrets()reject with avault not found: <vault>error for a vault it was not given, as they do on the Platform, instead of resolvingundefinedor{}. A missing secret in an existing vault still resolves toundefinedand is omitted fromgetSecrets(). A test that reads a vault it never seeded now fails; seed the vault withmockSecretmanager({ secrets: { "<vault>": { ... } } }), or with{}to test a missing secret.tailorRuntime({ config })seeds only the vaults declared indefineSecretManager(), so also seed vaults created withtailor secret vault createand the vaultstailor deploycreates for IdP clients.setSecrets()replaces andreset()clears config-loaded vaults too, so a test that calls them and then reads a config vault now fails; usesetSecret()ormergeSecrets()to add values while keeping those vaults.Patch Changes
#3027
20b75aaThanks @dqn! -tailor deploynow deletes the application of a config that no longer defines or references any TailorDB namespace, resolver namespace, IdP, or Auth service. Before, the application kept the services it was last deployed with, so it kept serving them, and a deploy that dropped one of those services deleted its tables or resolvers and then failed with... is used by applications. A config already in that state deletes its leftover application on the next deploy.deployasks for confirmation before deleting it, so a non-interactive run needs--yes.#2994
60bc80bThanks @dqn! - TailorDB migration diffs, and the schema drift detailstailor function runreports, now show foreign key changes on existing fields, such as~ ownerId: foreignKey: User.id → Person.id, instead of omitting them or printingconfiguration changed. In the schema drift details, a default value or create hook added to or removed from a field now shows asoptionalOnCreate: false → trueoroptionalOnCreate: true → false.#3011
5fcc3ceThanks @dqn! - Fix the "Event Payloads" section of the executor guide: it names the exported*Argstrigger args types instead of interfaces the SDK does not export, no longer lists ascheduledTimefield thatScheduleArgsdoes not have, and its resolver-executed examples narrow onsuccessso they type-check.#3012
ade7982Thanks @dqn! - Report an invalid Secret Manager vault or secret name, HTTP adaptername, AI GatewayauthNamespace, ortailor workflow executions --workflow-namevalue with the same message as OAuth2 and IdP client names: "must be 3-63 lowercase letters, digits, or hyphens, starting and ending with a letter or digit". Secret Manager names previously reported only the regular expression they failed to match.#3024
7a8bd33Thanks @dqn! - Stop saying that removed fields lose their data in thetailor tailordb migration resolve --rollbackwarning and in the suggestions fromtailor deployandtailor tailordb migration validate(namespace without a migration checkpoint) andtailor tailordb migration rebaseline(workspace tables that differ from the latest migration). They now say the fields are removed and only the deleted tables lose their data. The TailorDB migration guide also notes that a field removed bytailor tailordb migration syncmay come back with its earlier values when a migration adds it again.#2993
9634c2bThanks @dqn! - Internal refactoring: remove an unused field from howtailor deployplans workflow deletions. No user-facing behavior change.#2971
fbaf9b7Thanks @toiroakr! -tailor deploynow stops withSERVICE_IN_USEbefore it applies anything when the deploy would delete an Auth service that an application still references asexternal. Before, such a deploy deleted the Auth service's machine users and then failed on the Auth service itself, because the Platform refuses to delete an Auth service another application uses, which left the workspace half applied. This covers applications in the same deploy and applications that the deploy does not include. Keep the Auth service in the config that defines it, or move the referencing application to another Auth service in the same deploy.#3023
1a201faThanks @dqn! -tailor removenow also stops withSERVICE_IN_USEbefore it deletes anything when another application still references an Auth service it would delete, and bothtailor deployandtailor removestop the same way for a TailorDB namespace or resolver namespace that another application references asexternal. The error lists every application that uses each service. Before, they deleted the namespace's tables (with their data) or resolvers, or the Auth service's machine users, and then failed on the namespace or Auth service itself, because the Platform refuses to delete one that another application uses, which left the workspace half applied. Keep the resource in the config that defines it, or first remove the referencing applications or deploy them without it.#3009
52dafadThanks @renovate! - fix(deps): update dependency temporal-polyfill to v1.0.8#3022
1684419Thanks @renovate! - chore(deps): update dependency graphql to v17.1.0#2976
c24496dThanks @dqn! - Addcopilot,claude, andcodextotailor setup ci autofix --codemod. Each works asdeterministic, then hands what the codemods leave for review, with their migration prompts, to that AI coding agent in a job of its own,tailor-codemod-agent, which installs and runs none of the project's code. The fix commit carries the agent's edits aschore: apply the SDK upgrade with <agent>, leaving out.github/workflowsand, withclaude, the configuration files claude-code-action resets; if the agent fails, it carries only the codemods' rewrites. The agent runs on each push to a pull request from the repository while changes for review remain, except right after the workflow's own fix commit and for bots other thanrenovate[bot]; the warnings keep listing every change that was left for review. Claude and Codex read an API key from theTAILOR_AUTOFIX_ANTHROPIC_API_KEYorTAILOR_AUTOFIX_OPENAI_API_KEYrepository secret. Copilot reads a fine-grained personal access token fromTAILOR_AUTOFIX_COPILOT_TOKEN, or, with--copilot-auth github-token, signs in with the workflow token. The optionalTAILOR_AUTOFIX_CLAUDE_MODEL,TAILOR_AUTOFIX_CODEX_MODEL, orTAILOR_AUTOFIX_COPILOT_MODELrepository variable picks the agent's model.tailor setup ci envlists the secret, if any, and the variable, andtailor setup updatekeeps both flags. Withautofix-ciandsecurefix, an agent value moves the service's commit into thetailor-autofix-pushjob. Whentailor upgradeandtailor generatestill change files right after the workflow's own fix commit, the error says the agent's edits may be the cause, and on a pull request from the repository atailor-autofix-commentjob, withpull-requests: write, posts it as a pull request comment.#2989
b6fedd2Thanks @dqn! - Fixtailor deploy,tailor tailordb migration resolve, andtailor tailordb migration syncnot explaining how to proceed when records with no value for a field block changing it from optional to required.#3026
fc25c9fThanks @dqn! - TailorDB migration diffs, and the schema drift detailstailor function runreports, now show the same change details for a modified nested member as for a top-level field, such as~ address: members: ~zip (required: false → true), instead of only its path.v2.39.0Compare Source
Minor Changes
#2958
a955502Thanks @toiroakr! -defineAuthresults now haveasExternal(), which references an Auth service defined in another app of the same repository as an external one:auth: coreAuth.asExternal(). It takes over the name and the machine users, so the referencing app follows renames of both and gets the machine user names in its generatedtailor.d.ts. A misspelledinvokerthere is then a type error, which{ name: "...", external: true }could not provide because it leaves the names empty. Hooks, OAuth2 clients, and the rest of the definition are not taken over, so the referencing app does not deploy them again.#2952
93c373fThanks @toiroakr! -tailor deploynow stops withINVOKER_MACHINE_USER_NOT_FOUNDwhen a stringinvokerof a resolver or an executor names a machine user that does not exist in its Auth service. Before, a misspelled name passedtscanddeploy, and failed withmachine user not foundwhen the resolver or executor first ran. When a config deployed in the same run defines the Auth service, the machine users it lists are the ones accepted, because deploy removes the ones it no longer lists. When the Auth service is only referenced asexternal, the machine users that exist in the workspace are accepted. An existing config that names a machine user that exists nowhere now fails at deploy; add the machine user to the Auth service or fix the name. If you create the machine user of an externally referenced Auth service after deploying the app that uses it, deploy the Auth service first, or deploy both configs in the same run (tailor deploy --config a,b).#2975
5889f05Thanks @jackchuka! - Breaking change:tailor workspace pruneno longer accepts--personal. Every workspace now belongs to an organization, so there are no workspaces outside an organization and folder for it to select. Replace--personalwith--organization-rootor--folder-idnaming the locations to sweep. Do not just delete it: a--nameor--older-thansweep without a location considers every workspace visible to the login, even with--yes.#2739
8b69e57Thanks @toiroakr! -tailor seed applynow runs the TailorDB seed and the IdP_Userseed, list and delete scripts as temporary workflows instead of synchronous script executions, so they are no longer cut off by the 60-second execution limit. For each namespace it registers a function, a job function and a workflow namedtailor-seed-<kind>--<namespace>(<kind>istailordb,idp-seed,idp-listoridp-truncate), runs every chunk through them, and removes them afterwards. A namespace too long for the platform's 63-character name limit is cut short and followed by a hash. A run interrupted before cleanup leaves them behind, and the next run of the same script (the TailorDB seed, or the IdP_Userseed, list or delete) for that namespace removes them first.If
tailor seed applyfinds the workflow of an earlier run still executing (for example, a chunk that keeps running on the platform after Ctrl-C), it stops with an error naming the execution instead of removing it.tailor seed apply --truncateruns this check for every seed workflow of the namespaces it touches before it deletes anything, so an interrupted run no longer leaves a truncated table that is not reseeded. Wait for that execution to finish and run the command again. Runningtailor seed applyfor the same namespace in two processes at once is not supported: if one of them fails while registering the function, it removes the resources of the other. If the command loses track of a running chunk (for example, a timeout while starting it), it removes the resources and cannot tell whether the chunk was applied, so check the table, then re-run with--upsert.A TailorDB chunk that fails now stops the remaining chunks of that namespace, so later chunks do not fail on foreign keys of the rolled-back chunk or leave a gap in a table split across chunks.
The seed and seed dump scripts are now minified and, like other bundled functions, embed an inline sourcemap by default so error stack traces stay readable. Set
buildOptions.inlineSourcemaptofalseindefineConfigto drop the sourcemap.Patch Changes
#2981
1a4dca2Thanks @dqn! -tailor executor trigger --datanow delivers the JSON to an incoming-webhook executor as itsbody, as a request to the webhook URL does. Since a Platform change, the data had arrived one level deeper, underbody.body, so reading a field such asbody.emailreturnedundefinedwithout an error. If an executor readsbody.bodyto work around this, change it back tobody.--headervalues are not passed to the executor, which receives emptyheaders, and the command now warns when--headeris given.--headerwithout--datano longer sends a body, so the executor receivesbodyasnull, as with no options. To test an executor that reads headers, send the request to its webhook URL, whichtailor executor webhook listshows. The programmatictriggerExecutorpassespayloadto the executor asbodyunchanged, so pass the body itself rather than{ body, headers }.#2959
ebb62b6Thanks @dqn! -tailor generateandtailor function runnow read the config path fromTAILOR_CONFIG_PATHwhen--configis not given, like other commands that take a single config file. IfTAILOR_CONFIG_PATHholds comma-separated paths fortailor deploy, pass--configto these commands.#2960
61dbc34Thanks @dqn! -tailorRuntime({ config })now names the file, line, and parse error whentailor.config.tsor a file it imports does not parse, instead of reporting[object Object]againsttailor.config.ts.#2983
d4faf97Thanks @dqn! - Document that an executor with an incoming webhook trigger, when triggered manually withtailor executor triggerortriggerExecutor, receives norawBodyand emptyheaders, in the executor guide and in the JSDoc of the webhookrawBodyandheadersargs. An executor that verifies a signature overrawBodyrejects such a run, so test it through its webhook URL.#2957
b79b113Thanks @dqn! - Fixtailor deploy --no-schema-checkleaving a table removed from the local definitions without a migration until the next deploy when its namespace has pending migrations. The table is now deleted in the same deploy, after those migrations complete.#2941
7a5c244Thanks @dqn! -tailor deploynow prints the pending-migration summary and the other notices about the migration state (a checkpoint reset, tables left to delete, a migration to run again, a skipped script, ignoredsteps) once, before the plan, instead of repeating them after the confirmation. When the pending migrations change after the plan, for example because another deploy applied one, the deploy now stops withDEPLOY_PLAN_STALEinstead of applying a different set than the one it showed.#2987
67f8539Thanks @dqn! -tailor query --engine sqlandquery()from@tailor-platform/sdk/clinow report how many rows anINSERT,UPDATE, orDELETEchanged. For these statements the result addsaffectedRowsand setsrowCountto the same count, which was 0 when the statement had noRETURNING. When such a statement returns no rows, the text output prints the count (for example "3 rows affected.") instead of "No rows returned."#2988
818debcThanks @dqn! - Speed uptailor seed applyandtailor tailordb migration testfor a seed table too large for one chunk: splitting it took tens of seconds for a few MB of small records and now takes milliseconds#2961
f30a654Thanks @dqn! - Add--codemodtotailor setup ci autofix, so the autofix workflow handles the codemods of a pull request that upgrades@tailor-platform/sdk, such as one from Renovate. It upgrades each app from the version the base branch's lockfile resolves, or from 2.37.0 when the base branch has no such lockfile, to the version the pull request installs.warnreports whattailor upgradewould rewrite and the changes it leaves for review,errorreports them as errors and fails thetailor-codemod-resultjob, which also fails when the autofix job fails or is cancelled, anddeterministiccommits the rewrites with whattailor generatechanges and reports the rest.tailor setup updatekeeps the--codemodvalue, and without--codemodthe workflow is the same as before. Witherror, a review that still matches after you finish the migration keeps the check failing until the base branch has the new version.deterministicleaves files under.github/workflowsout of the fix commit and reports them for you to commit, and a bun repository needsbun.lockinstead ofbun.lockb.#2947
d372640Thanks @renovate! - fix(deps): update dependency kysely to v0.29.8#2951
ef7e152Thanks @renovate! - fix(deps): update @connectrpc to v2.3.0#2954
d065035Thanks @renovate! - fix(deps): update dependency @opentelemetry/semantic-conventions to v1.44.0#2955
0e86776Thanks @renovate! - fix(deps): update dependency @politty/zod to v0.7.1#2956
5f2bfc5Thanks @renovate! - fix(deps): update dependency globals to v17.14.0#2973
c0ae913Thanks @renovate! - fix(deps): update dependency semver to v7.8.6#2978
4dc187cThanks @renovate! - fix(deps): update oxc to v0.157.0#2997
d396c09Thanks @renovate! - chore(deps): lock file maintenance#2739
8b69e57Thanks @toiroakr! -tailor seed applynow runs each seed chunk in a single transaction. If any table fails, every table inserted earlier in that chunk is rolled back instead of being left committed, and Executors triggered by create events no longer run mid-chunk, which could deadlock on self-referencing tables.Seed data is split into chunks of about 3.5 MiB, and the transaction covers one chunk. A table that does not fit in one chunk is split across chunks and is committed chunk by chunk.
#2984
eb76277Thanks @dqn! - Labeling a closed pull request, such as one already merged, no longer deploys a preview workspace from the preview workflow thattailor setup ci preview --require labelgenerates. The cleanup workflow had already run when the pull request closed, so such a workspace stayed until a later cleanup run deleted it after its 7-dayttlexpired. Thetailor-preview-deployjob of every preview workflow now skips events on a closed pull request, and your jobs that need it are skipped with it.This release also raises the workflow template version, so
tailor setup checkreports a template-version finding for existing workflows until you runtailor setup update. WithTAILOR_PLATFORM_FAIL_ON_DRIFTset totrue, the drift check fails until then.#2982
cd33cdbThanks @dqn! - The v2 migration guide andtailor upgradeprompt for the programmatic CLI functions no longer say thattriggerExecutor'spayloadis typed from the executor definition.payloadis accepted only for an executor with an incoming webhook trigger, and its shape is not checked;startWorkflow'sargis still typed from the workflow definition.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.