Timmoth/RackPeek RackPeek-2.1.0 on GitHub

v2.1.0

Added a generic "Other" hardware type for devices that don't fit existing categories (radio bridges, KVMs, etc.), with full Web UI, CLI commands, and docs — requested by @AstroP25, contributed by @mavnezz (#244, #246)

Notes editor no longer loses characters or jumps the cursor while typing — reported by @robkreisel, fixed by @VirSanctus (#256, #316)
Docs page now loads correctly behind a reverse proxy, and all pages return proper HTTP status codes — reported by @maid450, with triage input from @hiSandog (#304)
New systems now save the system type shown in the dropdown instead of leaving it unset — reported by @mitchplze, with triage input from @hiSandog (#306)
Connections in imported YAML are now merged and shown in the import preview instead of being silently dropped — reported by @sjefferson99 (#308)
Published JSON schemas now match what RackPeek actually accepts (system.ip, server ports, connections section), so external validators and inventory generators agree with the API — reported by @ReevesJustin (#310, #311)
Fixed a crash on hardened Docker setups where /tmp isn't writable; login/session keys now live on the config volume and survive container upgrades — reported by @8thavenger (#312)
Deleting or renaming a resource no longer leaves dangling runsOn references and connections behind when the name is typed in a different case from the stored one — the resource was removed while every reference to it silently survived. Reported and fixed by @VirSanctus (#328, #329)

Documented Docker bind-mount permissions: RackPeek runs as UID/GID 1654:1654, so a bind-mounted host directory must be writable by that user, and SELinux systems need the :Z suffix — reported by @JamesBrianHill, contributed by @eli-sterling (#210, #317)

All NuGet packages updated to latest, fixing CI security-audit failures — Testcontainers bump by @VirSanctus (#315, #319)
Test suite hardened: fixed a flaky API test race, added E2E coverage for the new hardware type, and schema validation now runs against the published schemas so they can't drift again
E2E coverage expanded from 73 to 96 tests, closing every page that previously had none — docs, YAML view and import, SSH and hosts export, subnets, visualise, the tag and label pages, and the global connections page. The docs and YAML import tests double as regression guards for #304 and #308, both of which fail in ways that still render a working-looking page