Skip to main content

Releases and compatibility

Release governance lives beside the source code so the policies and the implementation change together. These GitHub documents are the canonical references:

  • Changelog — notable SDK, CLI, Scheduler, MCP, server, security, and documentation changes.
  • SDK compatibility policy — Semantic Versioning, supported runtimes, public entry points, and deprecations.
  • API versioning policy — /api/v1 compatibility rules and the boundary between public and operational endpoints.
  • Migration notes — database, configuration, CLI, API, media, and self-hosted upgrade steps.

The SDK and CLI are released independently with sdk-vX.Y.Z and cli-vX.Y.Z tags. The Scheduler and HTTP server should be deployed from one repository revision so their SDK behavior, OpenAPI documents, and database migrations stay aligned.

Current compatibility baseline​

  • @simple-post/sdk 1.x and @simple-post/cli 1.x require Node.js 20 or newer.
  • SDK 1.x publishes ESM, CommonJS, and TypeScript declarations.
  • Public HTTP integration endpoints use /api/v1.
  • Self-hosted Scheduler upgrades apply checked-in Prisma migrations with yarn prisma migrate deploy before the new application starts.

Do not rely on an old documentation subdomain. The public GitHub repository, package READMEs, checked-in OpenAPI documents, and the pages in this site are the supported documentation sources.