Skip to content

Update dependency @tailor-platform/sdk to v1.85.1 - #108

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailor-platform-sdk-1.x
Open

Update dependency @tailor-platform/sdk to v1.85.1#108
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailor-platform-sdk-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

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

v1.85.1

Compare Source

Patch Changes
  • #​2016 3af95bb Thanks @​toiroakr! - Remove a dead node:module import from a shared runtime helper chunk that could cause resolver bundling (and deploy) to fail with an UNRESOLVED_IMPORT error for projects importing @tailor-platform/sdk/runtime

v1.85.0

Compare Source

Minor Changes

  • #​1910 3153400 Thanks @​dqn! - Add an --upsert flag to seed. Without it, seeding a workspace that already holds some of the rows fails the whole batch for that type on the first duplicate id and inserts nothing. With --upsert, every TailorDB row must include an id; rows with new ids are inserted, rows with existing ids are updated, and omitted optional fields keep their stored values. Built-In IdP users are created or updated by name, with separate counts for each result. Default behavior is unchanged.

  • #​1891 1c323c3 Thanks @​dqn! - Add tailordb migration validate command that runs the same schema checks as deploy without applying anything: migration file integrity (including required migrate.ts scripts), local types vs. the latest migration snapshot, and remote schema vs. the migration checkpoint. Issues are reported per namespace with type/field-level detail, --json emits a machine-readable report, and the command exits with a non-zero code when drift is found, making it usable as a CI safety gate before deploying.

    As part of this, deploy's remote schema verification now propagates migration state lookup failures instead of silently skipping verification; only a not-yet-deployed namespace is still treated as a first apply.

Patch Changes

  • #​1911 62faf2f Thanks @​dqn! - Use each importing file's nearest tsconfig paths aliases as a fallback when bundling resolvers, executors, workflows, auth hooks, HTTP adapters, TailorDB hooks and validators, functions, seeds, queries, and migration scripts. A local dependency belonging to a different TypeScript project could previously leave an import unresolved when the bundle entry's project could not resolve it. Normal bundle resolution still takes precedence, so the importing file's aliases apply only when the import would otherwise be unresolved.

  • #​1911 8afbff1 Thanks @​dqn! - Fail the build when a bundled file imports a module that cannot be resolved. Previously such an import was silently left in the bundle and only failed at runtime after deploy, including when the tsconfig selected for the build did not declare an alias used by the source. The error names the unresolved specifier, the importing file, and the tsconfig.json the build used. Imports explicitly marked as external by a bundler, such as the platform-provided tailordb module, remain unaffected.

  • #​1937 648351e Thanks @​dqn! - Retry transient connection interruptions for read-only CLI requests

  • #​1920 26626e0 Thanks @​toiroakr! - Remove the undici dependency. Running the CLI no longer replaces the process-wide HTTP stack with a bundled undici build.

  • #​1928 0c97bc7 Thanks @​renovate! - fix(deps): update dependency globals to v17.8.0

  • #​1935 174eae9 Thanks @​renovate! - fix(deps): update dependency @​0no-co/graphql.web to v1.3.3

  • #​1936 54a2690 Thanks @​renovate! - fix(deps): update oxc

v1.84.0

Compare Source

Minor Changes

  • #​1860 50af713 Thanks @​dqn! - Fail deploy when a migration with breaking changes is missing its migrate.ts instead of silently leaving the migration unapplied while reporting success. Migration validation (missing scripts and schema checks) now runs while planning, so these failures also surface under --dry-run and before any resource is applied. Add tailordb migration script <n> --no-script --reason "..." to explicitly record that a migration needs no script; acknowledged migrations deploy their schema changes as usual and skip only the script step.

  • #​1906 db21d8f Thanks @​k1LoW! - Add Executor triggers for workflow and workflow job execution lifecycle events, with typed event arguments. Subscribing to these events is enough to receive them. deploy enables publishEvents on each targeted workflow, and on every job of a workflow targeted by a workflowJobExecution* trigger. Set publishEvents on createWorkflow / createWorkflowJob to publish without a subscribing executor, or to keep publishing off.

Patch Changes

v1.83.0

Compare Source

Minor Changes

  • #​1873 79f5d61 Thanks @​k1LoW! - Add tailor.workflow.execJobFunction as the canonical name for executing a workflow job function and returning its result. startJobFunction and triggerJobFunction remain available as aliases with the same behavior; @deprecated markers now point users at execJobFunction. Bundled workflow output emitted by the SDK now targets the canonical execJobFunction name.

  • #​1861 c970daf Thanks @​dqn! - Classify type-level unique index changes as breaking in tailordb migration generate: adding a unique index (or adding unique to an existing index, or changing a unique index's field set) now prompts for confirmation and auto-generates a migrate.ts that resolves duplicate value combinations before the constraint is enforced. During deploy, the pre-migration phase withholds the new unique index (or keeps the previous definition) until the migration script has run.

v1.82.0

Compare Source

Minor Changes
  • #​1866 1ae2485 Thanks @​toiroakr! - logLevel now also controls logger.* calls (from @tailor-platform/sdk/runtime) in bundled functions, in addition to console.*. logger.debug/logger.info/logger.warn/logger.error are dropped at the same thresholds as their console counterparts.
Patch Changes
  • #​1848 6f16760 Thanks @​toiroakr! - Replaced the table dependency (heavy transitive deps, low OpenSSF Scorecard) with an in-house single-line box-drawing table renderer used by the CLI's tabular output (logger.out, formatTable/formatKeyValueTable/formatTableWithHeaders). Column width calculation now uses the small, dependency-free get-east-asian-width package for correct alignment with full-width (CJK) characters. No user-facing behavior change is expected.

v1.81.0

Compare Source

Minor Changes

  • #​1824 617a263 Thanks @​haru0017! - Add a logger API for structured logging from Tailor Platform functions, exposing debug, info, warn, error, and setAttributes. The message is written to standard output, and the full entry with its attributes is exported over OpenTelemetry, where the attributes are queryable. Attribute values are typed to what OpenTelemetry can carry (string, number, boolean, and homogeneous arrays of those).

  • #​1718 d688c30 Thanks @​toiroakr! - Add permission field to createResolver for declaring a resolver's access requirement, using the same conditions/permit policy notation as TailorDB's .permission() (restricted to user operands, e.g. permission: [{ conditions: [[{ user: "_loggedIn" }, "=", true]], permit: true }]). Rejects non-matching callers before body runs. At least one permit: true policy is required (deny by default, granted only by a match); a matching permit: false policy always overrides that grant, for carving out an explicit exception. permission: "allowAnonymous" explicitly documents that anonymous callers are allowed. Omitting permission keeps prior behavior unchanged. tailor-sdk function test-run enforces the same guard.

Patch Changes

  • #​1797 93c1659 Thanks @​toiroakr! - Fix deploy reporting spurious updates on every run: TailorDB types no longer drift when the platform proto gains new fields, IdP services without an explicit userAuthPolicy no longer drift against the platform's default password policy, and deploys with pending migrations no longer silently skip type changes in namespaces that have no migrations

  • #​1842 b19c22b Thanks @​toiroakr! - fix(deps): update transitive dependency fast-uri to 3.1.4 [security]

  • #​1822 bcfc9ea Thanks @​renovate! - fix(deps): update dependency execa to v10

  • #​1826 bc85e4a Thanks @​renovate! - fix(deps): update oxc

v1.80.1

Compare Source

Patch Changes

  • #​1831 e24b3da Thanks @​toiroakr! - Fix IdPConfig's permission type so defineIdp calls with valid permission definitions using project-specific attribute keys are no longer rejected by tsc

  • #​1828 46f2d49 Thanks @​renovate! - fix(deps): update rolldown

  • #​1818 56608cc Thanks @​toiroakr! - Adopt Vitest 4.1 aroundEach/aroundAll hooks across the test suites, and update the TailorDB client mock example in the testing docs to the same style

v1.80.0

Compare Source

Minor Changes
  • #​1800 d07a82a Thanks @​toiroakr! - Machine user attribute keys now mirror the field's optionality: attributes derived from optional user fields (or optional machineUserAttributes fields) can be omitted, and null/undefined values 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 generated AttributeMap type used to read user.attributes in 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 f1cbda5 Thanks @​toiroakr! - Resolve each config's files glob patterns and bundler tsconfig relative to that config file's own directory instead of the invocation cwd, so --config a/tailor.config.ts,b/tailor.config.ts no longer lets one app's file glob or path aliases bleed into another. If a files pattern matches nothing under the new directory, it falls back to resolving against cwd as before, so existing configs whose patterns were written against the invocation directory keep working.

  • #​1821 d051132 Thanks @​toiroakr! - Resolve the bundler tsconfig for migration scripts, tailor query, and tailor function test-run from the owning config's directory instead of the invocation cwd, so path aliases keep working when the command runs against a config outside the current directory.

  • #​1767 c870196 Thanks @​toiroakr! - Fix tsconfig paths alias resolution for dynamically loaded resolver, executor, workflow, HTTP adapter, and TailorDB type files. Previously, an import like import { 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's paths aliases are now resolved as a fallback from its own tsconfig, based on the importing file's own directory.

  • #​1781 000db7e Thanks @​dqn! - Prevent concurrent multi-config deployments from mixing resolver, executor, workflow, Auth hook, HTTP adapter, and TailorDB hook or validator bundles

  • #​1793 a8f3e3a Thanks @​dqn! - Speed up deploy by running SDK version detection and function uploads concurrently

  • #​1785 cb97bd4 Thanks @​renovate! - fix(deps): update dependency tsx to v4.23.1

  • #​1805 62e5055 Thanks @​renovate! - fix(deps): update dependency @​oxc-project/types to v0.140.0

  • #​1823 605c1e5 Thanks @​renovate! - fix(deps): update dependency kysely to v0.29.4

  • #​1809 d8700fd Thanks @​dqn! - Fix deploy silently skipping a secret update after the remote value changed outside the current project directory (a deploy from another machine, or a console-side edit). Deploy now verifies each secret's last platform update time before skipping and re-updates the secret when it no longer matches. After upgrading, the first deploy re-pushes managed secrets once.

  • #​1806 8483dd0 Thanks @​dqn! - Fix concurrent deploys to the same workspace and application from one project directory causing a later deploy to silently skip a needed secret update. Secret and auth-connection updates are now serialized per workspace and application.

v1.79.0

Compare Source

Minor Changes
  • #​1800 d07a82a Thanks @​toiroakr! - Machine user attribute keys now mirror the field's optionality: attributes derived from optional user fields (or optional machineUserAttributes fields) can be omitted, and null/undefined values 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 generated AttributeMap type used to read user.attributes in 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 f1cbda5 Thanks @​toiroakr! - Resolve each config's files glob patterns and bundler tsconfig relative to that config file's own directory instead of the invocation cwd, so --config a/tailor.config.ts,b/tailor.config.ts no longer lets one app's file glob or path aliases bleed into another. If a files pattern matches nothing under the new directory, it falls back to resolving against cwd as before, so existing configs whose patterns were written against the invocation directory keep working.

  • #​1767 c870196 Thanks @​toiroakr! - Fix tsconfig paths alias resolution for dynamically loaded resolver, executor, workflow, HTTP adapter, and TailorDB type files. Previously, an import like import { 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's paths aliases are now resolved as a fallback from its own tsconfig, based on the importing file's own directory.

  • #​1788 da7d0c4 Thanks @​toiroakr! - tailor deploy no 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 cb97bd4 Thanks @​renovate! - fix(deps): update dependency tsx to v4.23.1

  • #​1801 ee382c7 Thanks @​toiroakr! - Update the tailordb erd plugin install hint to reference the renamed @tailor-platform/sdk-plugin-tailordb-erd package.

v1.78.0

Compare Source

Minor Changes

  • #​1753 6bff945 Thanks @​dqn! - Add typed, service-specific Vitest mock controls for runtime APIs and update generated project tests to use them.

  • #​1754 10392ff Thanks @​dqn! - Guide workspace selection and optional creation during deploy when no workspace is configured, with machine-readable recovery actions that preserve environment and profile settings

Patch Changes
  • #​1770 9ca5eaa Thanks @​toiroakr! - Document the type-level gqlOperations feature (.features({ gqlOperations }), including the "query" read-only alias) and the namespace-level db.tailordb.gqlOperations default in tailor.config.ts, clarifying that the namespace default also updates types that already exist on the platform.

v1.76.2

Compare Source

Patch Changes

  • #​1729 6c9cda3 Thanks @​dqn! - Run array field custom validators once against the complete array, skip custom validation when built-in type validation fails, and reject cloning validated fields between scalar and array shapes.

  • #​1735 a5f14a0 Thanks @​dqn! - Reject non-dot separators before fractional seconds in datetime field values.

  • #​1720 3d1c0f2 Thanks @​renovate! - Fix tailor-sdk setup generated workflows referencing tailor-platform/actions without the required sub-action path (e.g. /setup, /deploy), which broke generated GitHub Actions workflows after the v1.7.0 dependency bump. Also bring the coordinator workflow and local tailor-setup action templates up to the same v1.7.0 pin, which had been missed by the original bump.

  • #​1731 1e3de77 Thanks @​toiroakr! - Guard tailor-sdk remove against silently skipping a newly added managed resource type.

  • #​1725 4d724db Thanks @​dqn! - Fix tailor-sdk remove to delete managed workflow job function execution policies.

  • #​1715 5d7fd1a Thanks @​renovate! - fix(deps): update dependency type-fest to v5.8.0

  • #​1716 686c35d Thanks @​renovate! - fix(deps): update dependency undici to v8.7.0

  • #​1744 3ca5b48 Thanks @​renovate! - fix(deps): update dependency politty to v0.11.2

  • #​1745 fac7aff Thanks @​renovate! - fix(deps): update rolldown

  • #​1748 120fff3 Thanks @​renovate! - fix(deps): update dependency @​opentelemetry/semantic-conventions to v1.43.0

  • #​1750 57d81f3 Thanks @​renovate! - fix(deps): update dependency std-env to v4.2.0

  • #​1732 28fdb21 Thanks @​dqn! - Fix workflow trigger bundling for aliased imports, repeated local export names, and shadowed identifiers

  • #​1742 d0b0c2d Thanks @​toiroakr! - revert temporary pageSize limit for listWorkflowJobFunctions

  • #​1734 2c44645 Thanks @​dqn! - Fix secret and Auth connection deployments so local hash state cannot suppress updates in another workspace or application.

  • #​1731 2bdde6b Thanks @​toiroakr! - tailor-sdk deploy now validates AIGateway create/update requests against platform constraints before applying changes.

v1.76.1

Compare Source

Patch Changes

v1.76.0

Compare Source

Patch Changes

  • #​1701 e8bcbdf Thanks @​dqn! - Show the profile update --user recovery command when tailor-sdk login --profile authenticates a different user than the profile references.

  • #​1698 dd25b69 Thanks @​dqn! - Reject duplicate TailorDB type-level builder calls at type-check time and runtime instead of silently overwriting earlier settings.

v1.75.0

Compare Source

Minor Changes
  • #​1679 4ff2b23 Thanks @​k1LoW! - Add workflow job function execution policies. Declare them with defineWorkflowExecutionPolicies (or the single-key defineWorkflowExecutionPolicy), register them via workflow.executionPolicies on defineConfig, and pass the policy's key (or, for wildcard policies declared with matchType: "prefix", the value returned by keyFor(suffix)) through the new executionPolicyKey option on triggerJobFunction / job.trigger() to apply the platform-side concurrency cap. executionPolicyKey only accepts values produced by a declared policy. keyFor joins the prefix and suffix with . by default; override it with separator, passed as the second argument to defineWorkflowExecutionPolicies (applies to every policy in the group) or as a def field on a single defineWorkflowExecutionPolicy.

v1.74.1

Compare Source

Patch Changes

  • #​1669 6313353 Thanks @​dqn! - Preserve special characters when exporting TailorDB ERD viewer HTML and generated seed scripts.

  • #​1670 8c18c3b Thanks @​dqn! - Keep resolver and TailorDB field parsing behavior aligned.

  • #​1682 1e9ef08 Thanks @​toiroakr! - Fix a type error introduced in a previous release where an array field's .index()/.unique()/.clone()/pickFields() typing could become incompatible with itself when a field's shape flowed through an unresolved generic (e.g. a module-authoring helper's ReturnType<typeof genericFn> with no explicit type arguments). This could surface as a spurious TS2322/TS2345 type error when wiring a db.type() result produced by one generic helper into another.

  • #​1668 abcdca5 Thanks @​dqn! - Remove the obsolete MigrationInfo type export from @tailor-platform/sdk/cli.

  • #​1661 3ccbae3 Thanks @​renovate! - fix(deps): update dependency tsx to v4.22.5

  • #​1666 1d61fed Thanks @​renovate! - fix(deps): update @​opentelemetry

  • #​1667 2110fd1 Thanks @​renovate! - fix(deps): update dependency undici to v8.6.0

  • #​1675 15e721c Thanks @​dqn! - Refactor Vitest mock helpers without changing their public APIs or behavior.

v1.74.0

Compare Source

Minor Changes

  • #​1652 6c33b01 Thanks @​toiroakr! - Add tailor-sdk setup delete <file...> to cleanly remove generated CI workflow/action files together with their .github/tailor-sdk.lock entries. It only deletes files recorded in the lock, warns when an action is still referenced by a setup coordinate workflow, and removes the composite action's directory once it is empty.

  • #​1612 7e7f00e Thanks @​dqn! - Allow tailor-sdk deploy --config to accept comma-separated config paths so interdependent apps can be deployed together. Application, executor, workflow, workflow job, StaticWebsite, TailorDB, Auth, Auth connection, IdP, Resolver, AIGateway, and Secret Manager vault names must be unique across all configs passed to a single deploy, and resources still owned by another config in the same deploy are no longer deleted.

Patch Changes

v1.73.3

Compare Source

Patch Changes

  • #​1632 56cb49d Thanks @​dqn! - Validate that script expressions generated from TailorDB hooks and validators are valid JavaScript, failing at build time with a clear error instead of deploying broken scripts

  • #​1635 0af2c23 Thanks @​dqn! - Fix TailorDB relations silently dropping a forward relationship when two fields on the same type default to the same forward name; this now throws a validation error instead, matching the existing behavior for duplicate backward relationship names

  • #​1631 fffc654 Thanks @​dqn! - Fail with a clear error instead of producing corrupted bundle code when build-time source rewriting would apply overlapping edits

  • #​1630 69a034e Thanks @​dqn! - Fix workflow.trigger() calls in resolvers, executors, and workflow jobs failing at runtime when called without an options argument, or with options passed as a variable, a spread, or an object without a literal authInvoker property. All these forms are now rewritten at build time as the documented trigger(args, options?) signature promises; previously they compiled but threw "workflow.trigger() is rewritten at build time and unavailable in the bundle" after deploy.

v1.73.2

Compare Source

Patch Changes
  • #​1637 e608b6d Thanks @​toiroakr! - Bump the generated tailor-platform/actions reference pin to v1.5.1. The previous pin referenced a commit that could be orphaned by an upstream rebase; v1.5.1 fixes that issue.

v1.73.1

Compare Source

Patch Changes

  • #​1634 bab3cb0 Thanks @​dqn! - Fix TailorDB hooks and validators defined with method shorthand syntax (e.g. hooks: { create() { ... } }) failing at deploy time when the body contained an arrow function or the method was async

  • #​1614 8c6aff4 Thanks @​dqn! - Fix TailorDB schema drift detection during deploy to compare type settings, indexes, files, relationships, and permissions while normalizing SDK-derived deploy settings.

  • #​1628 ee21fd6 Thanks @​dqn! - Improve workflow type errors for invalid job and wait point definitions.

v1.73.0

Compare Source

Minor Changes

  • #​1625 0f23f78 Thanks @​toiroakr! - Add a runtime wrapper for AI Gateway. Resolvers, executors, and workflow jobs can now resolve an AI Gateway's platform-assigned URL by name via aigateway.get(name) (imported from @tailor-platform/sdk/runtime), instead of using the raw tailor.aigateway.get(...) global. Use mockAigateway() from @tailor-platform/sdk/vitest to mock it in unit tests.

    The gateway name is type-checked and autocompleted against the AI Gateways defined via defineAIGateway(), once tailor.d.ts has been generated (via tailor-sdk deploy/generate), mirroring the existing MachineUserNameRegistry/IdpNameRegistry/ConnectionNameRegistry pattern.

  • #​1608 89a29a2 Thanks @​k1LoW! - Add workflow.resumeWorkflow(executionId) to @tailor-platform/sdk/runtime for resuming a failed or pending-retry workflow execution from user code. mockWorkflow() in @tailor-platform/sdk/vitest gains a matching resumeWorkflow vi.fn and setResumeHandler helper for tests.

Patch Changes

  • #​1613 4b3d7c6 Thanks @​dqn! - Internal refactoring: deduplicate existing-resource fetching in the deploy command. No user-facing behavior change.

  • #​1615 5e1023c Thanks @​dqn! - Include the HTTP status, status text, and response body when a machine user token request fails, instead of a fixed generic message.

  • #​1611 ce51a97 Thanks @​dqn! - Ship unbundled type declarations so each .d.mts mirrors the source layout with real identifier names, instead of hashed chunks with minified aliases. JavaScript output stays bundled and the public API is unchanged.

v1.72.0

Compare Source

Minor Changes

✂ Note

PR body was truncated to here.

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 August 10, 2026 05:58
@renovate
renovate Bot force-pushed the renovate/tailor-platform-sdk-1.x branch from 1a3e18c to ac66c53 Compare August 16, 2026 00:03
@renovate renovate Bot changed the title Update dependency @tailor-platform/sdk to v1.85.0 Update dependency @tailor-platform/sdk to v1.85.1 Aug 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants