· 0.0.1-alpha.12
Authenticated triggers, bounded workflows and update discovery
Serve authenticated workflow endpoints, control Docker resource usage and see clearer run status and release information in Studio.
Before updating
Finish active and paused runs and verify retained-resource cleanup before updating. Stop services, back up state and validate workflows before restarting on this release.
Docker resource limits and dispatcher admission are opt-in and do not reserve host-wide memory. Existing installations receive no automatic limits.
Update discovery supports operator-managed updates; automatic activation, rollback and cross-version run recovery are not provided.
Changes
- Serve authenticated management APIs and Studio login with laufwerk serve, and define project HTTP triggers with durable submission deduplication.
- Set Docker CPU, memory, swap and process ceilings; prepare reusable Codex images and admit workflows within a persisted dispatcher capacity.
- Inspect queue reasons, environment preparation and retained resource-failure evidence in Studio, including keyboard and touch access to status details.
- Read remote release notes and assess update blockers in Studio or the CLI, with release history and JSON/RSS feeds for operators.
- Block dependency replacement while unfinished runs or finished runs with retained resources still require the current installation.
- Use consistent project identity validation across commands, including valid dotted IDs, and share passive project discovery and update safety checks.
Review compatibility in Studio or run laufwerk update --check with an updater-aware CLI. Older installations need an initial manual upgrade. Stop services and verify recovery before changing packages.