Skip to content

YA-WAMF 2.16.0

Choose a tag to compare

View all tags
@Jellman86 Jellman86 released this 25 Jul 22:04
· 557 commits to main since this release
v2.16.0
45937de
This commit was created on GitHub.com and signed with GitHub鈥檚 verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

YA-WAMF 2.16.0

YA-WAMF 2.16.0 makes everyday system state easier to read. It brings the desktop navigation closer
to the application鈥檚 calmer visual language, adds an honest live activity trace, and strengthens
the privacy and operational limits around opt-in aggregate telemetry.

What's new

  • See host activity without opening diagnostics. The sidebar鈥檚 system-status area now includes
    a lightweight one-minute trace of real CPU use and, where the host exposes a supported counter,
    active GPU or NPU utilization. Unsupported accelerator data is simply left out.
  • Navigate through a quieter, clearer sidebar. Observation and management destinations are
    grouped, the current route has a stronger Blue Tit treatment, connection state uses compact
    status rows, and account access is presented in a less prominent card.
  • Explore aggregate telemetry through purpose-built views. The public, aggregate-only dashboard
    now gives User Metrics and Health Data distinct layouts, accessible daily trends, responsive
    7/30/90-day views, and bounded categories that cannot be expanded by arbitrary reported values.

Smoother everyday use

  • Sidebar controls stay available on shorter screens. The navigation region scrolls
    independently, keeping account, notification, language, theme, and collapse controls reachable.
  • Opt-in telemetry is more defensive. Daily rollups avoid retaining unnecessary heartbeat
    history, opaque health-event identities make retries and restart overlap idempotent, and bounded
    request sizes, rate limits, write budgets, and incremental retention protect the ingestion
    service from malformed or excessive traffic.

Before you update

  • No special application migration is required. Back up /config and /data, then update the
    image normally. The telemetry service鈥檚 idempotent D1 migrations are applied by its deployment
    workflow and do not change an installation鈥檚 local database.
  • Keep the unsuffixed tag unless you intentionally use a smaller runtime image. latest and
    v2.16.0 remain the full compatibility build. Read the
    hardware-acceleration guide
    before switching to v2.16.0-cpu, v2.16.0-intel, or v2.16.0-cuda; change only the image tag
    so your existing /config, /data, models, and provider preference remain intact.

Good to know

  • The activity trace is intentionally lightweight. It requests one small live sample at a
    bounded interval, keeps only a minute in browser memory, and does not invent accelerator values.
  • Anonymous telemetry remains optional and aggregate-only. This release does not enable either
    telemetry channel for you. The public dashboard exposes fleet-level summaries, never installation
    IDs, hostnames, camera/media content, raw diagnostic messages, or credentials.

See the full changelog
for the complete technical record.

Assets 2
Loading