[agentHits]

What changed

pino 9.14.0 -> 10.4.0 and pino-pretty 11.3.0 -> 13.1.3 in all four workspaces that declare them (apps/dokploy, apps/api, apps/schedules, packages/server), plus bun.lock. No code changes.

Transitive updates pulled in by the bump: thread-stream 3 -> 4, real-require 0.2 -> 1.0, pino-abstract-transport 2 -> 3, fast-copy 3 -> 4, secure-json-parse 2 -> 4, strip-json-comments 3 -> 5. Each package still has a single copy in the lockfile.

pino-pretty 13.2.0 was published two days ago and is skipped by the 3-day release-age rule, so 13.1.3 is the newest eligible version.

How the logger is used

All three loggers (packages/server/src/lib/logger.ts, apps/api/src/logger.ts, apps/schedules/src/logger.ts) are created unconditionally with transport: { target: "pino-pretty", options: { colorize: true } }. pino-pretty is not dev-only: it formats the production container logs too. apps/dokploy has no direct imports; it uses the logger from @dokploy/server. The esbuild server bundle keeps packages external, so pino resolves the pino-pretty transport at runtime as before. No redact, custom serializers or multi-target transports are used.

Release notes

• pino 10.0.0: only breaking change is dropping Node 18 (we run Node 24). 10.1.0 switches the censor callback types (unused here). 10.1 to 10.4 are fixes: thread-stream v4, safer transport loading, worker thread names for transports, NODE_OPTIONS preload sanitising for workers, a default named export.
• pino-pretty 12.0.0: drops Node 14/16. 13.0.0: replaces readable-stream with the built-in stream. Neither renames options or changes transport behaviour.
• pino-pretty 13.1.0: "Add magenta as the color for printed object properties". With colorize: true the keys of logged objects are now wrapped in magenta ANSI codes. This is the only visible output change.

Verification

• Ran each of the three logger modules as the apps create them (Node 24, NODE_ENV=production, stdout piped, not a TTY) with info / object / format-string / error / err key / debug calls, before and after the bump. With ANSI codes stripped the output is byte-identical (timestamps, PIDs and stack line numbers normalised). The only raw difference is the magenta keys on object properties.
• Also ran packages/server logger under plain node (no tsx loader) to check the transport worker starts and flushes.
• bun run typecheck: all four workspaces pass.
• vitest run in apps/dokploy excluding *.real.test.ts: 2054 passed, 3 failed, all timeouts on a heavily loaded machine. better-auth-schema-compat and cloud-queue-availability pass when rerun alone with longer timeouts. env-file-literals needs a Docker daemon, which isn't available locally.
• biome check on the changed package.json files: clean.
• next build was not run locally; CI covers it.

Manual check on dev

• Check the dokploy, api and schedules container logs: lines still appear, errors show stacks, and there are no transport/worker startup errors.
• Anything that greps those logs for key: value may now see ANSI codes around the key. If that matters, set colorizeObjects: false in the pino-pretty options.

🤖 Generated with Claude Code