v2.12.0
gitroomhq/postiz-appv2.12.0Jan 14, 2026by nevo-david
AI Summary
Major infrastructure overhaul moving from BullMQ to Temporal, removing cron jobs, and updating Docker configurations for better state management and scaling.
Key Highlights
- Infrastructure migration from BullMQ to Temporal
- Removal of cron jobs and workers
- Synced workflow implementation
- Docker Compose updated to include Temporal
Breaking Changes
- Docker compose structure changed to include Temporal
- Postiz Docker image base changed from Alpine to bookworm-slim
- Docker Compose port exposure changed from 5000 to 4007
New Features
- New Temporal infrastructure for better state management
- Scheduled post tracking via Temporal UI
Full Release Notes
We have moved Postiz to a new infrastructure. Instead of using BullMQ for the queue, we are now using Temporal. We are paying off Postiz technical debt now, so we can soon deliver many, many awesome features. That means we no longer use an event-driven queue; we use a synced workflow. That allowed us to easily pass context between jobs, maintain state on failures, monitor them, and scale them. We also removed cron jobs and workers from the apps folder and replaced them with orchestrator. Before, when you posted something, it was added to different queues for webhooks and notifications — a total salad. If you have a problem, please report it ASAP. If you have a problem, please roll back to version: v2.11.3 Breaking changes you should know about. - Docker compose has changed to include Temporal, make sure you update it! - Postiz Docker no longer uses Alpine, as it's not supported by Temporal; we are now using bookworm-slim - We have a cron that moves posts from BullMQ to Temporal, so don't worry about scheduled posts. - You can track your scheduled posts on temporal ui at localhost:8080 - We changed the Docker Compose to expose port 5000 to 4007, because on many systems, port 5000 is taken. You can easily revert it in Docker Compose to port 5000.