Now I'll generate the release notes based on my understanding of the changes.

What's New

• Declarative container command and entrypoint — Set custom command/entrypoint on any project without a Dockerfile. Override the image default as an argv array, or omit to preserve the image default. Useful for stock images like cloudflare/cloudflared that need custom parameters.

• File injection into containers — Declare files to write into a container before it starts, on every recreate. Content can be inline (for configs) or sourced from a project env var at create time (for secrets). Files land with the octal mode specified (e.g. 0600 for a TLS key).

• New file management API — GET /api/projects/:id/files to list, POST to add/update (upserts by path), DELETE to remove files from a project.

• moor_deploy now supports command, entrypoint, and files — Pass them in a single operation. Files are additions/updates only — use moor_file_remove to delete.

• New MCP tools — moor_file_set, moor_file_list, moor_file_remove for declarative file management. Command and entrypoint parameters added to moor_project_create, moor_project_update, and moor_deploy.

How It Works

Files are written into the container via Docker's archive endpoint right before start, on every recreate. Command and entrypoint override the image defaults in the Docker create body — only set when provided, preserving the image default otherwise. Both features integrate seamlessly with existing build, redeploy, and cron workflows.

@moor-sh/mcp-v0.27.0 (2026-06-12)

Features

• api: declarative container command/entrypoint + file injection (#144) (2e8822a)

Fixes

• Fixed duplicate disk listings when bind-mounting a monitored path. The labeled monitored entry now takes precedence over the unlabeled container-visible duplicate.

What's New

• Monitored host disks — Configure MOOR_MONITORED_DISKS to bind-mount and report host filesystem usage alongside container-visible disks; appears in web UI, CLI stats, and MCP tool with optional friendly labels.

Improvements

• Disk monitoring now validates paths to prevent option injection (paths must be absolute and are passed with -- to df).
• Unmounted configured paths are skipped instead of reported as empty.
• Updated moor_stats MCP tool description to clarify it reports both container-visible filesystems and configured monitored disks.

Based on my review of the code changes, here are the release notes for v0.51.0:

What's New

• All filesystems visible — Server stats now report every mounted disk, not just root. Catches hidden volumes (e.g. a 344 GB database disk at 49% while root looked empty). Falls back to root if df --output is unavailable.
• Stats tab — New per-project tab shows live CPU, memory, network I/O, block I/O, and process count. Polled every 4 seconds while the tab is open.

Improvements

• Web, CLI, and MCP all surface the new disk and stats data.
• Backward compatible — the old single-disk disk field remains in /api/server/stats.

What's New

• Project history — View CPU, memory, and network metrics over the last hour, day, or week. Web UI includes lightweight sparklines and a timeline of lifecycle events. CLI command: moor history <project> [--hours N].

Fixes

• History argument parsing — moor history now accepts project name and --hours flag in any order. Previously --hours 1 project-name would silently misparse the flag value as the project ID.

Fixes

• Container orphan cleanup — When container creation succeeded but start or network attachment failed (e.g., port conflict), the container was left in Docker without a database reference, preventing project deletion from cleaning it up. Containers are now force-removed on start failure, with the original error always surfaced.
• Cleanup error reporting — removeContainer now throws on non-404 failures instead of silently logging, so cleanup logs accurately reflect whether orphan removal actually succeeded.

What's New

• Project history — Query container resource usage and lifecycle events over time with the moor_project_history MCP tool or the /api/projects/:id/stats/history API route.
• Resource sampling — Moor now records CPU, memory, network, and block I/O metrics every 60 seconds, with automatic 30-day retention.
• Docker event stream — Captures container lifecycle events (start, die, oom, kill, stop, restart) directly from Docker, so short-lived state changes are recorded rather than inferred from polling intervals.
• Container correlation labels — Every moor-created container now carries sh.moor.project_id and sh.moor.project_name labels for consistent event attribution.

Fixes

• moor_rebuild error reporting — The tool now surfaces actual error messages when /run fails before streaming output, instead of silently reporting "Rebuild complete" on validation errors or credential issues.

@moor-sh/mcp-v0.26.0 (2026-05-29)

Features

• monitored host disks via MOOR_MONITORED_DISKS (#140) (#141) (1d49890), closes #139

@moor-sh/mcp-v0.25.0 (2026-05-29)

Features

• api,web,cli,mcp: report all disks + live per-project Stats tab (#137, #138) (#139) (1bb3ae6)