v1.7.7 — Dashboard security and maintenance

v1.7.7 is a maintenance release for the BloxOS dashboard and project documentation.

• Update Next.js from 16.3.4 to 16.3.6, including the upstream next/og ImageResponse security fix. BloxOS does not use next/og, but ships the patched framework version.
• Update Framer Motion to 13.4.4 and Lucide React to 1.48.0.
• Align eslint-config-next with Next.js 16.3.6 and update the Node.js type definitions.
• Preserve the PostCSS 8.5.25 security override in the regenerated pnpm lockfile.
• Refresh the README introduction and screenshot gallery with current synthetic BloxOS views.
• Update installation and upgrade examples for v1.7.7.
• Update the pinned pnpm and Claude Code GitHub Actions.

Agent release 9 is unchanged from v1.7.6. Existing agents already running those bytes do not need an agent update or re-enrollment.

Update an existing installation

sudo bloxos-update update

For Docker Compose, set BLOXOS_VERSION=1.7.7, preserve your existing volumes and configuration, then follow the Docker installation guide.

Changes: v1.7.6...v1.7.7

v1.7.6 — Fleet power and rollout clarity

A focused hub and dashboard release that makes fleet power and agent rollout status easier to read.

• Show one concise Total power figure per machine on Overview, derived per machine and time window from complete CPU and GPU measurements.
• Keep the CPU, GPU, and Total breakdown on Machine Detail, including the integrated-graphics caveat where applicable.
• Refine Fleet Power with a stronger filled wave while preserving missing-data gaps.
• Improve Machine Detail power and critical-reading hierarchy.
• Make Versions rollout state clearer on desktop and mobile, show affected machines and blockers, and surface actionable agents first.
• Use the BloxOS mark as the browser favicon.
• Pin the pnpm and Claude third-party GitHub Actions to reviewed commit SHAs.

Agent release 9 is unchanged from v1.7.5. Existing eligible agents already running those bytes do not need an agent update.

Update an existing installation

sudo bloxos-update update

For Docker Compose, set BLOXOS_VERSION=1.7.6, preserve your existing volumes and configuration, then follow the Docker installation guide.

Changes: v1.7.5...v1.7.6

v1.7.5 — Maintenance updates

A maintenance release updating the hub database driver and dashboard dependencies.

• Update modernc.org/sqlite from 1.58.0 to 1.59.0 and its matching libc dependency.
• Update Framer Motion, Lucide icons, Tailwind Merge, Next.js ESLint configuration and React DOM types.
• Preserve the PostCSS 8.5.25 override and frozen-lockfile installation.
• Update the README and Docker installation examples for v1.7.5.

Agent release 9 is unchanged from v1.7.4. All three agent payloads are byte-identical; machines already running those bytes do not need an agent update. Existing staged delivery and signing requirements remain unchanged.

For an existing installation managed by the BloxOS updater:

sudo bloxos-update update

For Docker installations managed directly with Compose, follow the upgrade instructions and set BLOXOS_VERSION=1.7.5. Preserve existing data volumes and configuration.

Includes Docker images for Linux amd64/arm64, native server bundles for both architectures, the server updater, and agents for Linux amd64/arm64 and Windows amd64. The release passed full CI and Compose smoke; published image identities, server archive checksums, embedded agents and updater packaging were independently verified before publication.

Changes: v1.7.4...v1.7.5

v1.7.4 — Full fleet power history

BloxOS v1.7.4 fixes the 24-hour fleet power chart's history cutoff and updates the server, dashboard and agent dependencies.

Fixed

• Fleet power history reads the full selected period instead of stopping at 20,000 records. Even seven continuously reporting machines can exceed that old limit in one day.
• History records are streamed into chart aggregates, with cells grouped by chart bucket to reduce memory use and repeated scans.
• Explicit capped diagnostic reads no longer report false truncation on an exact fit, hide truncation when a payload is corrupt, or show a partially read bucket as a fleet total.
• Interrupted or timed-out reads return an error rather than a successful partial chart. Current power remains independent of the selected history period.

Power remains machine-reported component telemetry. Missing readings stay unavailable; domains are never added together, and legacy modelled readings remain labelled and separate. This release does not enable energy or cost estimates.

Dependencies

Includes Next.js 16.3.4, matching React and React DOM 19.3.0, Framer Motion 13.2.0, Lucide 1.44.0, and updated Go dependencies. The PostCSS 8.5.25 override is preserved.

Update the server

If the host updater is configured, run on the BloxOS server:

sudo bloxos-update update

Or use Settings → Updates → Update BloxOS. For first-time updater setup, follow the system update guide. Manual Compose installations can set BLOXOS_VERSION=1.7.4 and follow the upgrade instructions. Preserve existing volumes, configuration and installation keys.

After upgrading, confirm both server components show v1.7.4, then reopen the 24-hour fleet power chart. Missing sensor data and genuine collection gaps can still appear; reading the full window does not establish complete sensor coverage.

Agents

Both server packages include agent release 9 for Linux amd64, Linux arm64 and Windows amd64. The number increases from release 8 because the agent dependencies changed.

Eligible agents follow the existing automatic staged rollout after the server update. Check Versions for progress, pauses or withheld reasons. A completed server update does not mean every agent has finished updating. Agent rollback protection remains forward-only; rolling the server back does not downgrade agents that already accepted release 9.

Verification

The exact tagged commit passed release CI, including the full hub race suite, Linux and Windows agent tests, dashboard validation and Compose smoke. Release asset checksums, source revision and bundled agent identities were checked before publication. This verifies the release artifacts; it is not a claim that this release has already been deployed to your fleet.

Source: 3550cd9de9212b2150b047ee01ba20fa3e6fc6d7 · Changes since v1.7.3

v1.7.3 — Lumen visual finish

BloxOS v1.7.3 brings the Lumen visual finish to the dashboard: a wider desktop workspace, readable typography and controls, clearer tables, and consistent hierarchy across Overview, Machine Detail, Inventory, AI Sessions and Versions.

Fixed

• Machine Metrics distinguishes loading, failed requests, confirmed empty history and a single data point. Retry keeps the selected period; a failed refresh retains the last loaded readings with an explicit warning.
• Dark and Bright accent controls use the correct foreground contrast, including keyboard-focused menu items.
• Responsive shell, machine tables and power charts receive the reviewed visual finish. Power scope, coverage warnings, separate metric units, permissions, machine actions and saved preferences remain intact.

Update the server

With the host updater already configured, run on the BloxOS server:

sudo bloxos-update update

Or use Settings → Updates → Update BloxOS. If the worker is not installed, follow the one-time setup. Manual Compose installations can set BLOXOS_VERSION=1.7.3 using the upgrade guide. Preserve the existing project, volumes, signing identity and Caddy CA.

Agents

This release carries agent release 8, byte-identical to v1.7.2, for Linux amd64, Linux arm64 and Windows amd64. Agents already matching that build do not need another update. Eligible older agents follow the existing staged rollout; check Versions for progress or a withheld reason. A missing installation signing key cannot be repaired by publishing a new server release; use the documented trusted recovery procedure when needed.

Verification

The exact release commit passed the full CI suite, including hub race tests, Linux/Windows agent tests, dashboard tests/lint/build and Compose enrollment smoke. Published archive checksums, source revision and all three bundled agent payloads were verified before final publication. UI screenshots are controlled demo captures, not a claim of live-fleet hardware validation.

Source: b4f8364bcfca54c8b44b99766035dbf4d137bb0b · Changes since v1.7.2

BloxOS v1.7.2

Agent updates follow server updates

BloxOS server releases now include the Linux x86-64, Linux ARM64 and Windows x86-64 agent payloads. Standard native and Compose installations offer the bundled agent after the server update. Each platform rolls out automatically: one canary, then batches of two, with continuous telemetry required before proceeding.

Agent release 8 adds stricter counter availability checks and reports the existing Linux virtualization host/guest role. Existing explicit binary overrides and installation-specific signature authorization remain respected. An offline-signing installation must authorize the exact new payloads before its agents can update.

Power reporting you can interpret

• A fleet Power column and machine Overview readings show System, CPU package, GPU total and DRAM separately as 30-second means.
• Current readings expire consistently. Missing, stale, clock-skewed, ambiguous or incorrectly scoped readings remain unavailable; genuine supported zero readings remain zero.
• Agents no longer generate estimates. Historical modelled readings remain readable and explicitly labelled, separate from measured series.
• RAPL requires every participating counter to progress; backward steps and incomplete groups produce gaps. Known guests do not report RAPL as physical-machine power. Generic board-sensor and battery readings no longer claim whole-system scope. In-band DCMI requires an active reading.
• Charts preserve gaps and isolated observations, use distinct measured/modelled lines, and keep every control visible on narrow screens.
• Energy and cost are withheld because existing sampled windows cannot establish observed duration.

Release reliability

Managed payloads are checked for platform, hash, size and embedded release identity. Release identities cannot be reused with changed bytes. Native archives are deterministic, and partial publication retries reuse the verified image pair.

Upgrade

On the BloxOS server, use Settings → Updates → Update BloxOS, or run:

sudo bloxos-update update

Wait for the server update to finish, then check Versions for agent rollout progress. A paused, halted or unauthorized platform does not silently count as updated. Unsupported power sensors remain unavailable; this release does not invent readings for machines without usable counters.

The updater preserves the database, keys and installation identity. Rolling the server back does not downgrade agents that already advanced their durable release floor. Sensor availability checks do not certify calibration.

Source: 5ba21326d3c3393d7672ef017cbf05d994eddb96 (reviewed integration PR #239). Release artifacts are published only after release verification and Compose smoke pass.

BloxOS v1.7.1

Release verification passed. Native payloads are extracted from the published image; operator review and final release notes are pending. Fleet signatures are installation-specific and are not included.

BloxOS v1.7.0

Release verification passed. Native payloads are extracted from the published image; operator review and final release notes are pending. Fleet signatures are installation-specific and are not included.

BloxOS v1.6.0

Release verification passed. Native payloads are extracted from the published image; operator review and final release notes are pending. Fleet signatures are installation-specific and are not included.

BloxOS v1.5.0

Release verification passed. Native payloads are extracted from the published image; operator review and final release notes are pending. Fleet signatures are installation-specific and are not included.