Version Packages (next)#1804
Open
tailor-platform-pr-trigger[bot] wants to merge 2 commits into
Open
Conversation
commit: |
tailor-platform-pr-trigger
Bot
force-pushed
the
changeset-release/v2
branch
2 times, most recently
from
July 17, 2026 07:02
e9ff219 to
adf614a
Compare
This comment has been minimized.
This comment has been minimized.
tailor-platform-pr-trigger
Bot
force-pushed
the
changeset-release/v2
branch
from
July 17, 2026 07:09
adf614a to
eb906e0
Compare
This comment has been minimized.
This comment has been minimized.
20 tasks
tailor-platform-pr-trigger
Bot
force-pushed
the
changeset-release/v2
branch
2 times, most recently
from
July 18, 2026 00:48
de61b01 to
8441bcf
Compare
This comment has been minimized.
This comment has been minimized.
tailor-platform-pr-trigger
Bot
force-pushed
the
changeset-release/v2
branch
from
July 18, 2026 08:48
8441bcf to
f94c9f2
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v2, this PR will be updated.
v2is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonv2.Releases
@tailor-platform/create-sdk@2.0.0-next.7
Major Changes
#1782
c971797Thanks @toiroakr! - RenameWorkflow.trigger()(returned bycreateWorkflow()) andWorkflowJob.trigger()(returned bycreateWorkflowJob()) to.start(), aligning the SDK's ergonomic verb with the platform'sstart*RPC vocabulary:const inventory = checkInventory.trigger({ orderId: input.orderId }); +const inventory = checkInventory.start({ orderId: input.orderId }); -const workflowRunId = await orderProcessingWorkflow.trigger(args, { invoker: "manager" }); +const workflowRunId = await orderProcessingWorkflow.start(args, { invoker: "manager" });mockWorkflow()'swf.job(definition)/wf.workflow(definition)now return a mock of the.startmethod, andwf.setTriggerHandler/wf.triggeredJobsare renamed towf.setStartHandler/wf.startedJobs. No codemod ships for the.trigger()→.start()call-site rename itself — see thev2/workflow-start-renamemigration guide entry for manual migration steps.Minor Changes
e349b9eThanks @dqn! - Add lint rules that flag the external /api prefix in HTTP adapter path patterns and permission settings that grant access unconditionally, and enable them in newly scaffolded projects.@tailor-platform/sdk@2.0.0-next.7
Major Changes
#1782
c971797Thanks @toiroakr! - RenameWorkflow.trigger()(returned bycreateWorkflow()) andWorkflowJob.trigger()(returned bycreateWorkflowJob()) to.start(), aligning the SDK's ergonomic verb with the platform'sstart*RPC vocabulary:const inventory = checkInventory.trigger({ orderId: input.orderId }); +const inventory = checkInventory.start({ orderId: input.orderId }); -const workflowRunId = await orderProcessingWorkflow.trigger(args, { invoker: "manager" }); +const workflowRunId = await orderProcessingWorkflow.start(args, { invoker: "manager" });mockWorkflow()'swf.job(definition)/wf.workflow(definition)now return a mock of the.startmethod, andwf.setTriggerHandler/wf.triggeredJobsare renamed towf.setStartHandler/wf.startedJobs. No codemod ships for the.trigger()→.start()call-site rename itself — see thev2/workflow-start-renamemigration guide entry for manual migration steps.#1782
c971797Thanks @toiroakr! - Remove the pre-alignmenttailor.workflownamestriggerWorkflow,triggerJobFunction, andresumeWorkflow(and theirTriggerWorkflowOptions/TriggerJobFunctionOptionsoption types) from@tailor-platform/sdk/runtime, the ambient@tailor-platform/sdk/runtime/globalstypes, and themockWorkflow()test facade. Use the canonical names instead:import { workflow } from "@tailor-platform/sdk/runtime"; -await workflow.triggerWorkflow("myWorkflow", { data: "value" }); +await workflow.startWorkflow("myWorkflow", { data: "value" }); -workflow.triggerJobFunction("myJob", { data: "value" }); +workflow.startJobFunction("myJob", { data: "value" }); -await workflow.resumeWorkflow("execution-id"); +await workflow.resumeWorkflowExecution("execution-id");Run the
v2/workflow-trigger-renamecodemod to migrate call sites automatically.Minor Changes
d07a82aThanks @toiroakr! - Machine user attribute keys now mirror the field's optionality: attributes derived from optional user fields (or optionalmachineUserAttributesfields) can be omitted, andnull/undefinedvalues are treated as "attribute not set" instead of being rejected at deploy time. Attributes derived from required fields remain mandatory, and undeclared attribute keys are still rejected. The generatedAttributeMaptype used to readuser.attributesin resolvers, executors, and workflows now mirrors this same optionality, so an attribute derived from an optional field is typed as possibly absent instead of always present.Patch Changes
#1741
f1cbda5Thanks @toiroakr! - Resolve each config'sfilesglob patterns and bundlertsconfigrelative to that config file's own directory instead of the invocationcwd, so--config a/tailor.config.ts,b/tailor.config.tsno longer lets one app's file glob or path aliases bleed into another. If afilespattern matches nothing under the new directory, it falls back to resolving againstcwdas before, so existing configs whose patterns were written against the invocation directory keep working.#1767
c870196Thanks @toiroakr! - Fix tsconfigpathsalias resolution for dynamically loaded resolver, executor, workflow, HTTP adapter, and TailorDB type files. Previously, an import likeimport { foo } from "@/utils"in one of these files would fail to resolve when the file lived outside the directory tsx was registered from (e.g. in multi-app setups). Each file'spathsaliases are now resolved as a fallback from its own tsconfig, based on the importing file's own directory.#1788
da7d0c4Thanks @toiroakr! -tailor deployno longer automatically deletes on-disk bundle artifacts left by SDK versions predating the in-memory bundling approach; delete those specific stale files manually if any remain from a very old SDK version (do not delete the whole output directory, which also holds deploy state such as secrets and Auth Connection records)#1785
cb97bd4Thanks @renovate! - fix(deps): update dependency tsx to v4.23.1#1801
ee382c7Thanks @toiroakr! - Update thetailordb erdplugin install hint to reference the renamed@tailor-platform/sdk-plugin-tailordb-erdpackage.@tailor-platform/eslint-plugin-sdk@0.1.0-next.0
Minor Changes
e349b9eThanks @dqn! - Add lint rules that flag the external /api prefix in HTTP adapter path patterns and permission settings that grant access unconditionally, and enable them in newly scaffolded projects.@tailor-platform/sdk-plugin-tailordb-erd@0.1.0-next.1
Minor Changes
ee382c7Thanks @toiroakr! - Renamed the package from@tailor-platform/sdk-tailordb-erd-pluginto@tailor-platform/sdk-plugin-tailordb-erd, following theeslint-plugin-*-style naming convention used for CLI plugin packages. Update your dependency to the new name; thetailor-tailordb-erdexecutable and thetailor tailordb erdcommands are unchanged.Patch Changes
f1cbda5,c870196,d07a82a,da7d0c4,cb97bd4,ee382c7,c971797,c971797]:@tailor-platform/sdk-codemod@0.3.0-next.7
Patch Changes
#1787
898d0b0Thanks @toiroakr! - Fixtailor upgradereporting zero codemods across several v2 prerelease boundaries.v2/db-type-to-tableandv2/runtime-subpath-namespacenow trigger at2.0.0-next.4(where they actually shipped) instead of2.0.0-next.3, andv2/forward-relation-name,v2/tailordb-validate-simplify, andv2/tailordb-hook-redesignnow trigger at2.0.0-next.5instead of2.0.0-next.4.#1787
6653afdThanks @toiroakr! - Add aV2_NEXT_PENDINGplaceholderprereleaseUntilfor codemods whose exact2.0.0-next.Nrelease boundary isn't known yet at implementation time, plus apnpm codemod:resolve-pendingstep (wired into the release workflow) that resolves it to the real version constant once the release PR bumps@tailor-platform/sdk's version. Prevents codemod boundaries from drifting out of sync with the version they actually ship in, which previously required a manual follow-up fix after each release.#1782
c971797Thanks @toiroakr! - RenameWorkflow.trigger()(returned bycreateWorkflow()) andWorkflowJob.trigger()(returned bycreateWorkflowJob()) to.start(), aligning the SDK's ergonomic verb with the platform'sstart*RPC vocabulary:const inventory = checkInventory.trigger({ orderId: input.orderId }); +const inventory = checkInventory.start({ orderId: input.orderId }); -const workflowRunId = await orderProcessingWorkflow.trigger(args, { invoker: "manager" }); +const workflowRunId = await orderProcessingWorkflow.start(args, { invoker: "manager" });mockWorkflow()'swf.job(definition)/wf.workflow(definition)now return a mock of the.startmethod, andwf.setTriggerHandler/wf.triggeredJobsare renamed towf.setStartHandler/wf.startedJobs. No codemod ships for the.trigger()→.start()call-site rename itself — see thev2/workflow-start-renamemigration guide entry for manual migration steps.#1782
c971797Thanks @toiroakr! - Remove the pre-alignmenttailor.workflownamestriggerWorkflow,triggerJobFunction, andresumeWorkflow(and theirTriggerWorkflowOptions/TriggerJobFunctionOptionsoption types) from@tailor-platform/sdk/runtime, the ambient@tailor-platform/sdk/runtime/globalstypes, and themockWorkflow()test facade. Use the canonical names instead:import { workflow } from "@tailor-platform/sdk/runtime"; -await workflow.triggerWorkflow("myWorkflow", { data: "value" }); +await workflow.startWorkflow("myWorkflow", { data: "value" }); -workflow.triggerJobFunction("myJob", { data: "value" }); +workflow.startJobFunction("myJob", { data: "value" }); -await workflow.resumeWorkflow("execution-id"); +await workflow.resumeWorkflowExecution("execution-id");Run the
v2/workflow-trigger-renamecodemod to migrate call sites automatically.