v1.7.1

MirrorProxy v1.7.1

MirrorProxy v1.7.1 polishes the rebuilt v1.7.0 interface, fixing numerous visual details and usability issues across the public portal and administration console, while improving download-token setup and Agent installation compatibility.

Interface refinements after the v1.7.0 redesign

The v1.7.0 redesign introduced a new portal and administration console; this
release addresses the rough edges found in real use. Login no longer pre-fills
the administrator name. Invitation history and mirror health tables receive
consistent styling. Account pages have aligned headings and actions, clearer
identity sections, shared footers, smaller traffic statistics, and responsive
session and download-token tables without nested vertical scrolling. Download
grants identify users and explain permission and inheritance behavior. Text
contrast and security-settings heading structure are improved in both themes.
Loading, errors, retries and action feedback are clearer across management
screens. Chinese and English interfaces remain supported.

Highlights

• Present user and group download grants with identifiable names and clear revoke behavior. Preserve inherited permissions and existing authorization controls.
• Display a newly created download token once, alongside copyable shell-specific setup commands. The CLI prompts on interactive stdin and continues to accept piped tokens.
• Refine account and administration forms, invitation history, mirror health tables, session records and mobile layouts. Add consistent public-page footers and improve text contrast and heading semantics.
• Extend Agent setup compatibility and fix Windows installer behavior.

Security and compatibility

Existing configuration, routes, database and download authorization remain compatible. The npm audit retains a temporary exception for GHSA-gcqx-w48m-w2h4, affecting the deepmerge build-tool dependency; other advisories still fail the audit. Remove this exception when a compatible upstream fix is available.

Upgrade using the matching release artifact and verify its published checksum before replacing the executable. Preserve the configuration and database. Roll back by restoring the previous executable if necessary.

Verification

Release validation includes locked Rust checks, frontend build and browser tests, administration smoke tests, and dependency audits. Consult the CI run for the release commit for exact results.

Full comparison: v1.7.0...v1.7.1