Skip to content

Releases

Latest stable

The current published stable release is

v6.1.6

. All @hellmai/lumenflow-* packages are published together. See the Changelog for the full history.

v6.1.6— 2026-08-18

v6.1.5— 2026-08-18

v6.1.4— 2026-08-18

v6.1.3— 2026-08-18

v6.1.2— 2026-08-16

v6.1.1— 2026-08-16

v6.1.0— 2026-08-16

v6.0.18— 2026-08-14

Version-alignment release (no new changes since the previous tag).

v6.0.17— 2026-08-14

v6.0.16— 2026-08-14

For the full release history, see the Changelog.

Connected Compute runner packages are promoted by evidence, not by intention:

  • Private test artifact: named testers may use a one-time bootstrap or local artifact path.
  • Internal release: operators may use a versioned internal artifact after service wrapper, doctor, start/stop, drain, rollback, and uninstall evidence exists.
  • Public package manager: npm, WinGet, Homebrew, MSI, .pkg, .deb, .rpm, or tarball install commands appear only after the release manifest and smoke evidence verify that channel.

If a release note does not name a public runner package channel, use the documented private or internal setup path for that release. The general @hellmai/lumenflow-cli package remains the workflow CLI; it is not proof that every connected-runner package channel has shipped.

To pull the latest version:

pnpm lumenflow:upgrade --latest

Every release is verified with a fresh install, not just an internal build: before @hellmai/lumenflow-cli is published, an automated check installs it (and every @hellmai/lumenflow-* package it depends on) into a clean environment exactly the way npm install would for a new project, then runs lumenflow init, wu:create, wu:claim, and wu:prep against that install. The same check also verifies upgrading from the latest 5.x release and from the previous 6.x release lands cleanly on the new version, so pnpm lumenflow:upgrade --latest is exercised before it ever reaches a real project.

LumenFlow follows Semantic Versioning:

  • Major versions (X.0.0) may include breaking changes
  • Minor versions (0.X.0) add features, backwards compatible
  • Patch versions (0.0.X) fix bugs, backwards compatible

When pulling across major versions, check the Compatibility Matrix for supported Node.js and package-manager versions, and the Changelog for any notable changes.