Changelog

What actually shipped.

Pre-launch changelog — Publishly is in active build toward launch. Entries below are dated development milestones, not versioned releases, and every bullet maps to real work in this repository.

By Liam, founder of Publishly · Published 2026-08-10

Quick answer

Publishly has not launched yet — this changelog covers two days of build so far. 2026-08-09 was the initial platform build on the open-source Postiz engine; 2026-08-10 repositioned the product around delivery reliability with a documented failure catalog, signed failure webhooks, publishing-job receipts, a new flat pricing model & a rebuilt marketing site.

2026-08-10AddedChanged

Failure catalog: every publishing failure now classifies into one of 20 documented codes across three classes — recoverable, needs-your-action, content problem.
Signed post.failure webhooks: a failed post fires an HMAC-signed event carrying the failure class, code, reason & whether Publishly will retry.
Publishing-job receipts: each destination tracks its own delivery state history, with the provider post ID & live URL stored on success.
New pricing model: flat tiers sized by monthly post volume, with unlimited connected accounts on every paid plan — replacing per-account pricing logic.
Marketing site rebuilt around the reliability story: docs-as-citation error pages, this changelog, and platform reference pages generated from the real failure catalog and provider code.

2026-08-09Added

Initial Publishly platform build, forked from the open-source Postiz engine (AGPL-3.0).
Marketing site stood up alongside the in-app product.
Security hardening pass across authentication, encrypted token storage & scoped API keys.
Background publishing that keeps scheduled posts moving after the browser closes.

No invented version numbers and no back-filled feature dates — when a claim here needs backing, it maps to data/public-product-facts.json or the commit history of this repository.