UnENVerse Find a guide: importing, command line, nodes

All releases

UnENVerse 2026-10-09 (0.42.x)

The product is now UnENVerse everywhere: the crates and folders are unv-cli and unv-server, the desktop package is unenverse, release archives are named unv-<version>-<platform>, the data directory is io.unenverse, the per-directory context file is .unv.json, browser-storage keys start with unenver…

Changed

  • The product is now UnENVerse everywhere: the crates and folders are unv-cli and unv-server, the desktop package is unenverse, release archives are named unv-<version>-<platform>, the data directory is io.unenverse, the per-directory context file is .unv.json, browser-storage keys start with unenverse-, and calendar event ids end in @unenverse. The ENVV_* environment variables are no longer read; use UNV_*.
  • The container image is published as ghcr.io/<owner>/unenverse/unv-server.
  • The licence is now Apache-2.0.
  • The README is rewritten for new users; this changelog replaces its history table.

Added

  • unv node install: sets up a managed node in one command (system user, hardened service, file access limited to the named targets, reload through a root-owned path unit, optional loopback relay to the hub). --plan shows the steps.
  • Every release now attaches unenverse-<version>.vsix, the VS Code extension, which is versioned with the rest.

Fixed

  • unv --env-file now reads the UNV_PASSWORD and UNV_SERVER_URL entries of a compose .env.
  • Node targets with a rooted path such as /etc/x are accepted on Windows.
  • Windows and Linux CI: node end-to-end tests no longer race the hub's poll stamp, the history snapshot test no longer depends on scheduling, Rust formatting is enforced by npm run preflight before a push, and the Linux build job installs the mold linker.

·