Fluent CLI v2.2.4 - Safer Installs & CI/CD Config
Release
Author:
Marco Heuer
Changed on:
19 Oct 2026
| Target release date: | 2026-10-19 |
|---|---|
| Release status: | Released |
Description
Adds an`env()` template function and opt-in profile bootstrapping for CI/CD pipelines, scrubs personal data from MCP GraphQL responses, and makes module and blueprint installs report asset failures instead of success.Changelog
- Added an `env(VAR)` template function so module config values, such as webhook authentication, can be sourced from CI/CD environment variables. Only variables matching `--env-prefix` (default `FLUENT_`) are resolved, and missing or disallowed references fail with a single aggregated error
- Added `--skip-bootstrap` to `profile create` and a new `profile bootstrap` command, so granting roles and applying account settings is opt-in instead of a side effect of creating a profile
- MCP `graphql_execute` responses are now scrubbed of personal data before they reach the AI assistant. Setting values are exempt, so manifests and security headers can still be read, edited and saved
- Added `--strict` to `blueprint install`, and asset install failures are now reported per module instead of as "installed successfully"
- Added x/y progress and an ETA while loading products during `module install`
- Added a warning when a later workflow fragment replaces or deletes a ruleset from an earlier module, and `workflowlog describe` now lists ruleset names and merge strategies
- `module install` `--include`/`--exclude` file entries are now scoped per asset folder and matched exactly, including sub folders. A file level `--exclude` skips only that file instead of the whole asset folder
- `module install` skips empty or malformed JSON assets and empty plugin JARs with a warning instead of crashing the run
- Debug logging now redacts credentials in arguments, metadata, errors and messages
- `setting get` now defaults `--context` to retailer, and `event list` warns that `--retailer` does not filter and `--size` is capped at 100
- Fixed rejected entity upserts being reported as success; they now appear in the end-of-run summary and fail the run under `--strict`
- Fixed the workflow log being written when the workflow upload is rejected, and `workflowlog insert` overwriting existing entries
- Fixed network updates only adding locations; locations removed from the network definition are now removed
- Fixed template replacement dropping falsy-but-valid values such as an empty string
- Fixed `module install` crashing when the workflow log setting has a null value
- Fixed the MCP workflow tools failing with ENOENT on Windows
| Released capability depth: | Enhancement |
|---|---|
| Release bundle / Capability type: | Tool |
