Skip to content

Minimal Router OS v0.1.5 (Beta)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Aug 08:04
· 7 commits to main since this release
v0.1.5
80a84a1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Minimal Router OS v0.1.5

Status: Beta / controlled pilot

v0.1.5 moves the approved dashboard design into the appliance production frontend and adds a focused set of operator-facing reliability controls without expanding MinimalRouter into a general-purpose network platform.

Highlights

  • Production dashboard uses the v0.1.5 visual system rather than a demo-only overlay.
  • GitHub Pages demo and production use the same dashboard components and final CSS; demo mode differs only in mocked data and explicitly demo-only states.
  • Mobile navigation uses a fixed top-right control and a pushed/scaled foreground-page interaction inspired by Noema's mechanics, while retaining MinimalRouter's own colors, typography and navigation design.
  • The mobile menu closes with the same control, Escape, an exposed-page click or section navigation and restores the previous scroll position when appropriate.
  • Desktop frame uses one exact 37 px gutter at the viewport/sidebar edge, between sidebar and content, and at the far-right content edge.
  • The redundant Gateway healthy Overview ribbon chip is removed while the separate topbar health control remains available.
  • Logs startup diagnostics use a horizontal milestone timeline on desktop and a horizontally scrollable sequence on mobile.
  • Connected devices can show Online, Last seen and New state from existing bounded DHCP/accounting data.
  • A LAN device can have Internet access paused for 15 minutes, 1 hour, or until resumed. Timed pauses use nftables kernel timeouts and the privileged helper validates the address against its trusted last-good LAN configuration.
  • Gateway Health exposes three fixed recovery actions: Reconnect WAN, Restart DNS & DHCP, and Restart WireGuard. The dashboard cannot select arbitrary services or execute shell commands.
  • Gateway history records sampled WAN availability/outages and bounded public-IP transitions locally. The UI reports partial coverage honestly until a full 30-day history exists.
  • Recovery/backup/pfSense migration tools are presented from the Recovery workspace rather than being mixed into Security.

Dashboard validation

The release candidate includes Playwright regression coverage for both the production and GitHub Pages demo builds, including:

  • fixed mobile menu position while scrolling;
  • pushed-page menu geometry and close behavior;
  • scroll restoration;
  • every dashboard route fitting the mobile viewport without page-level horizontal overflow;
  • production/demo mobile behavior parity;
  • desktop 37 px frame geometry;
  • removal of only the redundant Gateway ribbon chip;
  • horizontal startup timeline behavior on desktop and mobile.

Installation and startup validation

The exact release-candidate commit must pass the complete Golden ISO gate. That gate extends the existing clean-disk installation test with:

  • installed-disk cold boot without the ISO attached;
  • proof that firstboot does not run again;
  • real SSH and Dashboard/API readiness after cold boot;
  • forced routerd crash followed by supervise-daemon recovery;
  • warm reboot followed by another full readiness check;
  • refusal to overwrite a disk that already contains MinimalRouter;
  • refusal to install onto an undersized 4 GiB disk before destructive writes begin.

The final release artifacts are published only from the signed release workflow after the exact tagged commit passes the release validation path. The release publishes the tested AMD64 Golden ISO and checksum, signed AMD64/ARM64 distribution archives and manifests, SPDX SBOMs, SHA256SUMS, and GitHub attestations.

Scope and pilot status

v0.1.5 remains a Beta / controlled pilot release. CI/QEMU qualification is deliberately broader than v0.1.4, but it does not replace real Proxmox + ISP validation. Before unattended use, the owner lab should still verify real PPPoE reconnect/reboot behavior, WireGuard recovery, DDNS/public-IP changes, timed device-pause expiry, power-cycle behavior and the established pfSense fallback path.

Assets 11
Loading