Community / System Ops

Changelog

All notable changes to system-ops are documented here.

[Unreleased]

Contributor, support, security, conduct, and governance policies; issue forms, PR template, review routing, and agent instructions.
Public documentation generated from maintained Markdown, searchable navigation, and a refreshed marketing site.
Documentation/link validation and release preparation guidance.
Disposable Ubuntu/systemd release fixture covering the installer, account permissions, background updater, and recovery.
Static-host configuration and grouped documentation/configuration directories.

Match the public site and documentation to the console’s dark monochrome theme, with square controls and text-only navigation.
Batch routine dependency updates monthly per ecosystem; reserve major upgrades for manual review and keep security alerts enabled.
Redesigned the public site with a light product-led layout, warm gradients, interactive console screenshots, installation tabs, resource navigation, and matching documentation styling.
Group community policies under .github/, documentation by purpose under docs/, and build/test/type configuration under config/; preserve public documentation URLs.
Standardized maintainer/package metadata and Node 24 version files.
Replaced unverified installer/marketing memory promises with reproducible measurement guidance.
Use the MIT-licensed UA Parser v1 line; dependency automation excludes its AGPL v2 line.

Compatible SPA fallback routing and trusted asset roots after the Express 5 upgrade, which otherwise prevented startup and returned 404 from hidden updater staging directories.
Align React and React DOM after the React 19.3 update; group their future dependency updates to prevent incompatible runtime pairs.
Recovery now uses staged validation instead of resetting the checkout or clearing Git stashes.
Re-running the installer delegates to staged updates; local installs clone committed source instead of copying secrets or worktree pointers.
Synthetic benchmark logs rotate at a bounded byte limit during long runs.
Long workload requests remain authenticated beyond browser-session expiry.

Maintainer waived the 24-hour acceptance gate and requested closure of the remaining reliability tracker. No long-running or production availability result is claimed.

Stop tracking built dist/ in git — deploy and Docker build produce assets locally
Narrow default sudoers rules (journalctl, tail, ufw, fail2ban, docker, systemctl, certbot, deploy/recover scripts)
Installer no longer sets BACKUPS_DIR by default — configure when backups are ready
docker-compose.yml env vars aligned with APP_PASSWORD and current .env.example

Edit this page on GitHub Need help?Source: docs/releases/CHANGELOG.md