Flare 0.6.5

Flare 0.6.5

Source commit: a2ed02e0085df283fd1a6a685b97fad3b6377b78.

Features

• Add the navigation editor with list, form and batch views, category management,
  icon selection, unsaved-change protection, version-conflict handling and draft
  export/restore. Improve Chinese and English editor localization.
• Add configurable search engines and hybrid search, category navigation and
  mobile/desktop layout controls.

Correctness and reliability

• Escape navigation text and attributes and enforce supported URL/image schemes.
• Keep dynamic URL metadata request-local, preserve encoded redirects and source
  context, and fix IPv6 and Base64 handling.
• Preserve authentication settings when unrelated environment values are invalid;
  repair deprecated boolean CLI aliases and validate unsafe request sources.
• Preserve failed editor/settings submissions and guard recovery data against
  unintended default-file initialization.
• Refresh weather asynchronously with coalescing, stale snapshots and failure
  backoff; avoid showing fabricated values before data is available.
• Make static resource caching safe across upgrades with content-derived ETags
  and versioned resource URLs.

Performance

• Reuse immutable parsed configuration/navigation snapshots, reduce category
  rendering work and avoid processing hidden modules or unmatched icons.
• Reduce editor filtering, repeated row construction, listeners and dirty checks.
• Cache immutable resource metadata and avoid loading the host MIME registry for
  bundled assets.
• In the documented default-data Linux benchmark, CPU per request fell
  59.6–81.1% and allocated bytes per request fell 55.2–94.5% versus pre-audit main
  39df281 (not 0.6.4). RSS was mixed; some HTML cases increased 0.5–3.3%.
  See the full report.

Upgrade notes and limitations

• Back up the complete data directory, Compose/environment settings and external
  secrets before upgrading; test restoration separately.
• Unsupported URL protocols remain in stored data but render as #. Icons
  accept bundled identifiers or absolute HTTP(S) image URLs. Administrator Footer
  HTML remains trusted administrator content.
• Per-entry private flags do not enforce per-entry access control. Protect a
  private deployment with whole-site authentication.
• Reverse proxies must preserve the request context needed by protected writes.
  Full subpath hosting is not implemented.
• Physical Safari/Via/Android/iPad acceptance remains unverified.
  This release proceeds with that validation limitation explicitly disclosed;
  automated Chromium coverage does not certify those physical environments.
• CPU/allocation improvements do not establish universally lower retained memory,
  browser latency or ARM performance.

Documentation now covers configuration precedence, backup/recovery, proxy limits,
troubleshooting, development builds and measurement methods.

Installation and verification

docker pull soulteary/flare:0.6.5
# Or use GitHub Container Registry:
docker pull ghcr.io/soulteary/flare:0.6.5

Both registries publish linux/amd64, linux/arm64, linux/arm/v7 and
linux/arm/v6. Version and latest tags were independently verified through
anonymous registry reads to share this manifest digest:

sha256:44948e8c1c3d4c4743cd1db907993feec89362391f69ea87ed9d75a0710b60bf

All seven downloadable archives passed checksum, architecture, toolchain,
version and commit checks. The published Linux amd64 archive executable and
extracted image executable passed HTTP smoke tests. A disposable sample-data
0.6.4 → 0.6.5 upgrade, restart and restored-backup rollback preserved configuration,
navigation data, authentication and session continuity. These checks do not
constitute a Docker-engine container run or ARM/physical-device acceptance.

Release workflow
completed successfully, including the four-platform GHCR mirror verification.