Skip to content

animaEngine 1.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 18 Aug 11:58
· 430 commits to main since this release
v1.0.0
14515ad

animaEngine 1.0.0

The stable 1.0 release. animaEngine renders multiple animated characters
over your Linux desktop — transparent, click-through, GPU-accelerated,
X11 and native Wayland — in Rust on wgpu + winit. No Electron, no
Chromium.

This is the end of a three-candidate bake (rc1 → rc3) plus an external
security/robustness audit. rc3 ran as a public prerelease for about two
weeks with no regressions. What changed across the candidates is in
CHANGELOG.md; the short version is that every error
path got probed, a memory soak came back flat, and the issues an audit
found — a broken single-instance handshake, a config loader that could
panic or overwrite your scene, a Shimeji importer that followed
symlinks, a thumbnail path escape, live dependency advisories, and an
AppImage that linked too-new a glibc — are all fixed.

Highlights

  • Overlay that behaves. Click-through by default; the ⚙ button and
    panels stay interactive. Always-on-top, skips the taskbar, no focus
    steal. X11 (XShape/EWMH) and native wlroots layer-shell.
  • Drop to add. PNG / GIF / WebP / JPEG / MP4, with size and
    dimension caps enforced before decode.
  • Shimeji import, tray icon, global hotkeys, multi-monitor.
  • Durable config. Atomic writes, schema migration with backups, and
    a hot-reload that never overwrites your file on a bad edit.
  • Honest supply chain. SBOMs embedded in every artifact, build
    provenance attestation, a strict dependency-audit gate.

Install

  • .deb (Debian/Ubuntu) and AppImage (built on glibc 2.35, runs
    on every current mainstream distro) from this release's assets. Verify
    with the attached SHA256SUMS.
  • Flathub and AUR follow shortly after this tag (they publish
    from separate repositories).

See install-verification-1.0.md for the
from-scratch install checks per channel.

Thanks

To everyone who ran the candidates on their actual desktops and filed
what broke. That's what made the bake worth doing.

What's next

Cross-platform: BSD, then Windows, then macOS, via an OverlayPlatform
abstraction — the overlay layer is the only OS-specific part. The plan is
in cross-platform-plan.md.

Assets 5
Loading