Latest stable
The current published stable release is
v1.0.122. All @hellmai/lumenflow-* packages are published together. See the
Changelog for the full history.
Releases
Recent releases
Section titled “Recent releases”v1.0.122— 2026-10-31
v1.0.121— 2026-10-31
v1.0.120— 2026-10-30
v1.0.119— 2026-10-30
v1.0.118— 2026-10-30
v1.0.117— 2026-10-30
v1.0.116— 2026-10-30
v1.0.115— 2026-10-30
v1.0.114— 2026-10-29
v1.0.113— 2026-10-29
For the full release history, see the Changelog.
Connected Compute runner availability
Section titled “Connected Compute runner availability”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.
Upgrading
Section titled “Upgrading”To pull the latest version:
Release verification
Section titled “Release verification”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 previous published release lands cleanly
on the new version, exercising pnpm lumenflow:upgrade --latest before it ever reaches a real
project. The check additionally verifies upgrading from the latest 5.x release and the previous
6.x release, when that pre-rename version history exists for the published package name — today it
does not for @hellmai/lumenflow-cli, so only the previous-published-to-current leg runs.
Backwards compatibility
Section titled “Backwards compatibility”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.