Mastra 1.63.0 injects trace_id and span_id into native log records and gates deployment on worker readiness
Released 28 August, Mastra core 1.63.0 adds an AdaptableLogger contract so loggers write trace_id and span_id into their own native records during traced operations, with the observability LogEvent derived from the same record and the legacy dual-write wrapper deprecated. PinoLogger implements it via a pino mixin so trace context reaches stdout, files and custom transports. The deployer now ships a dedicated worker entry with a /health endpoint returning 503 during startup and 200 once workers initialize, and workers discover schedules created after startup without a restart; a separate fix stops a tool resumed with a falsy payload (false, 0, empty string) from staying suspended and dispatching a duplicate background run.
↳ Follow the thread