VacuumStream v0.2.1

VacuumStream 0.2.1

A packaging release. The application behaves exactly like 0.2.0; what changed is the metadata and
the build inputs that a store needs in order to build VacuumStream from source.

Store metadata

• The AppStream metadata now carries screenshots, brand colours, an age rating, device support
  hints and per-release notes, so software centres can present the application properly.
• Four screenshots taken from the running application live in docs/images/.

Building from source offline

• flatpak/package-lock.json ships an npm lockfile generated from package.json without the
  end-to-end test runner, whose browser downloads an offline build never uses. Bun remains the
  development package manager.
• scripts/flatpak-node-sources.sh regenerates that lockfile together with the Flatpak node
  sources used by a network-less build.
• Maintainer documentation describes the Flathub build path alongside the existing bundle build.

Install

Download the AppImage or Flatpak attached below, plus SHA256SUMS:

sha256sum --check --ignore-missing SHA256SUMS

For AppImage:

chmod +x VacuumStream-0.2.1-x86_64.AppImage
./VacuumStream-0.2.1-x86_64.AppImage

For Flatpak 1.16 or newer:

flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install --user ./VacuumStream-0.2.1-x86_64.flatpak
flatpak run io.github.eliottness.VacuumStream

See the user guide
for FUSE alternatives, controller setup, and Steam Gaming Mode.

Validation and limitations

• bun run verify passes on the tagged commit: lint, type checking, the unit suite and a
  production build. GitHub CI ran the same verification on this commit.
• The Flathub manifest built by flatpak-builder produces a working application: the packaged
  binary starts and renders the home screen with live Twitch data.
• VacuumStream is still not published on Flathub. The submission is prepared but not accepted.