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.

Published packages and hosted features​

The docs pin and check published SDK 1.3.3. CLI 1.3.3 requires SDK ^1.3.3 for local publishing, while posts to Scheduler-connected accounts execute on the hosted app.

This release includes the shared media and final-content validation fixes, complete Threads carousels, and rejection of unsupported YouTube playlist assignment before upload. Local video publishing requires FFmpeg's ffprobe on PATH, or an absolute FFPROBE_PATH. Failed inspection blocks sending. See the migration notes and validation coverage.

Check your installed package version and its tagged release notes for later hosted changes. Self-hosted behavior follows the revision you deploy.

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.

Documentation release checklist​

  • Export both API references, billing facts, and platform rules from the core checkout being released using yarn docs:export in core. The checked-in docs-source.json records its revision and source hash.
  • Run yarn sync:sdk and yarn check:sdk to verify the pinned npm reference and executable quickstart independently of the core checkout.
  • Update affected user guides and integration examples. Keep hosted account setup separate from developer credentials and deployment-specific capabilities.
  • Run docs type checking, a production build, and yarn check:workspace with sibling core and website-social checkouts. The website must be built for rendered trial CTA verification.
  • Verify desktop and mobile help links, search, assistant setup, and expired-trial recovery wording. Opening a plan preference must never start checkout automatically.
  • Publish matching app, landing, and docs revisions. Verify https://docs.simplepost.social canonical URLs and path-preserving redirects from the former domain.