upstream-twenty/packages/twenty-sdk/CHANGELOG.md

Changelog

All notable changes to the Twenty SDK are documented in this file.

The format follows Keep a Changelog, and this package adheres to Semantic Versioning.

[Unreleased]

Added

• enqueueJobs in twenty-sdk/logic-function. Enqueues one run per payload of a single logic function in one call (up to 200 payloads per batch). retryLimit and delayMs apply to every run in the batch.

  import { enqueueJobs } from 'twenty-sdk/logic-function';
  
  await enqueueJobs({
    logicFunctionUniversalIdentifier: PROCESS_BATCH,
    payloads: batches.map((batch, batchIndex) => ({ batchIndex })),
  });
  

Deprecated

• enqueueJob in twenty-sdk/logic-function. Use enqueueJobs with a one-element payloads list instead. enqueueJob keeps working for now and will be removed in a future major version.

Changed

• twenty-client-sdk should now be a dev dependency too. Although app code imports it (CoreApiClient, MetadataApiClient, RestApiClient), Twenty provides it at runtime — logic functions get it from a generated SDK layer and front components resolve it from server-served modules — so the installed copy is only needed for typechecking and the deploy-time build. Newly scaffolded apps now place it under devDependencies. Moving it is recommended (not required: the server already strips it from the deployed runtime), and keeps the installed app leaner:

    "dependencies": {
  -   "twenty-client-sdk": "^2.13.0"
    },
    "devDependencies": {
  +   "twenty-client-sdk": "^2.13.0"
    }
  

  twenty build now also emits a warning when twenty-client-sdk is still listed under dependencies.

[2.8.0]

Breaking Changes

• twenty-sdk must now be a dev dependency. It ships the twenty CLI and the build/scaffolding tooling, which only run at development and build time — it is never imported by a published app's runtime. Newly scaffolded apps already place it under devDependencies. Apps created before 2.8.0 must move it when upgrading:

    "dependencies": {
      "twenty-client-sdk": "^2.8.0"
  -   "twenty-sdk": "^2.8.0"
    },
    "devDependencies": {
  +   "twenty-sdk": "^2.8.0"
    }
  

  Then reinstall with rm -rf node_modules && yarn install. twenty-client-sdk stays under dependencies because app code imports it at runtime.

  twenty build now emits a warning when twenty-sdk is still listed under dependencies, so existing apps are flagged automatically.