Omniplex
Affected components
Issues have been resolved, post mortem will be posted soon
The v1.5.0 release included a new public endpoint, GET /changelogs/@all, as part of the new curated changelog system. Its route definition declared a query parameter (project) without a required Schema field. Our API framework validates every route's parameters at startup and panics immediately if one is malformed so instead of failing gracefully or only affecting that one endpoint, the entire process crashed before it could start serving traffic at all.
Caught via Dokploy's application logs showing the container repeatedly exiting, with a clear panic trace pointing directly at the offending route registration.
Added the missing Schema field to the project parameter, matching the convention used by every other query parameter in the codebase. Verified the fix resolves the panic and the full test suite still passes before redeploying.
This route was new in the same release and wasn't exercised by a startup/smoke test before deploy the panic only surfaces when the process actually boots and registers its routes, which local go build/go vet/unit tests don't exercise the same way.