Commerce core in Go and PostgreSQL: catalog with simple, configurable, bundle, kit, grouped, digital and subscription products, custom options, carts, checkout, orders with partial fulfillment, a payment ledger, refunds and credit memos, inventory with reservations, promotions, tax, gift cards, store credit, loyalty, referrals, wishlists and reviews.
Skelet 0.2.0
First in this changelog, released 2026-10-18 - 9 entries. Every release
First public release, and where this changelog starts. The v0.1.0 and v0.1.1 tags came
before anyone outside the project ran Skelet, so their history lives in git rather than here.
A fresh clone comes up as a working shop, so trying it is cheap. The plugin SDK, the remote-provider contract and the product each carry their own version, so a plugin states its own compatibility range instead of tracking the platform.
Added9
Two GraphQL surfaces, admin and storefront, with separate schemas, so storefront introspection can’t see an admin operation.
Multi-channel and multi-locale throughout: one catalog serving several storefronts in different currencies and languages, with per-channel listings, permissions and settings.
Content: a block-based CMS, a blog, URL rewrites and redirects, web forms and a product feed for merchant platforms.
Admin dashboard in React, with staged saves, saved views, split panes and language packs, and a reference storefront in Next.js.
Signals, an optional analytics suite in its own process and database: Lens for web analytics and session replay, Synapse for customer profiles and segments, Pulse for email campaigns and flows, Prism for experiments. Its event spine lives in ClickHouse, and
SIGNALS_ENABLED=falseruns the commerce side alone.Plugins compiled into the binary from their own Go modules (
./skelet cli plugin add), with an SDK at0.1.0, plus remote providers over a versioned wire contract for shipping and promotions. Offline payment methods are built in; card gateways are plugins.Platform: a runtime config registry with encrypted secrets, integration tokens, HMAC-signed webhooks, a transactional outbox, scheduled jobs with retries, search on Postgres or OpenSearch, bulk import and export, image transforms, and object storage on S3 or a local directory.
Operations: everything in containers, a small single-container deployment shape and a split production one, health and readiness endpoints, and opt-in OpenTelemetry and Sentry.
