Changelog

ReleaseFlow now publishes its privacy policy and terms at /privacy and /terms, linked from every footer.

Download pages show a Buy button that starts ReleaseFlow checkout when the app sells a Polar product.

The marketing site was rebuilt around what ReleaseFlow replaces: manual appcasts, update feeds and license servers.

List, read and update license status over REST and MCP. Keys stay masked and there is no delete or email path.

Apps can serve a separate portal download channel next to the public releases.

Affonso referrals are carried from the landing page into checkout metadata and reported on order.paid.

The landing footer lost its dead # links: Help Center became a mailto, Documentation points at /api/docs, Pricing at /pricing.

A Swift licensing SDK with per-machine trials, opt-in device tracking and a key management page.

A token-gated DEV channel lets you ship builds to testers without exposing them publicly.

License key creation is available from the REST and MCP APIs, not just the dashboard.

Machine license state works for every provider, with rate limiting and dialogs for device actions.

Downloads and update feeds resolve to a compatible platform release, so an app fetch never lands on an asset it cannot run.

Release notes served inside Sparkle keep their text readable in dark mode.

The full ReleaseFlow MCP surface is exposed with OAuth, and legacy OAuth tables still resolve.

Downloads pick the right architecture when a release ships more than one build.

Download responses keep Content-Length intact, so Electron and Sparkle updates show real progress again.