Boomi Companion changelog
The Boomi Companion changelog highlights top updates per month. Releases containing only internal changes are omitted from the changelog.
For the full list of changes, refer to:
June 2026
bc-datahub - Versions 0.1.1 – 0.2.5
We added these features
- bc-datahub plugin and boomi-datahub skill - Initial release of
bc-datahub, a new plugin that lets you configure and manage Boomi Data Hub directly through Boomi Companion. Supports common operations including models, sources, deployments, quarantine, and golden records. - Model tag support - Added support for applying tags to Data Hub models, enabling better organization and filtering across repositories.
- Repeating field group support - Added support for repeating field groups and repeating single fields, expanding the range of model structures
bc-datahubcan handle. - And more...
We fixed these issues
- Silent componentId parse failure -
datahub-connection.shno longer silently fails to parse thecomponentId; the deploy/undeploy argument order was also unified for consistency.
Checkout June 2026 commit history
bc-integration - Versions 1.0.4 – 1.0.22
We added these features
- Process Route support - Added support for Process Route, a new integration capability.
- Database (Legacy) connector reference - Full reference added for the Database (Legacy) connector, covering connection, operation, database profile, and step, plus Document Cache component coverage for the profile.
- And more...
We fixed these issues
- Silent XML corruption on component create/push - Fixed a defect where component create/push corrupted the XML when the
<?xml ?>declaration shared a line with the<bns:Component>root element.
Checkout June 2026 commit history
May 2026 - Versions 0.5.50 – 1.0.3
We added these features
- Boomi Companion 1.0.0 GA — Official 1.0 launch at Boomi World 2026.
- Mail (IMAP) connector reference — Full reference for SMTP outbound + IMAP inbound, covering connection (Basic Auth + OAuth 2.0), all three operations (Receive, Send, Move), Document Cache attachment routing, and the Receive-as-start-step listener pattern. All claims runtime-validated.
- Component-type workspace layout — The
active-development/folder now uses Boomi's own component-type identifiers (e.g.process/,connector-action/) instead of generic plural names. New types are discovered automatically. Includes a UI-label-to-identifier table for non-obvious mappings (Connection→connector-settings,Operation→connector-action,Map→transform.map). - Environment Extensions CLI (
boomi-extensions.sh) — New script for managing Environment Extensions values with partial-by-default writes and pre-write snapshots to prevent accidental overwrites. Process Extensions reference documentation also sharpened. - And more...
Checkout May 2026 commit history
April 2026 - Versions 0.5.21 – 0.5.49
We added these features
- API Service Component (REST) reference — Full reference for the Integration-native deployable that wraps WSS Listen processes for Advanced-runtime deployment, including the silent-404 failure mode, cascade deployment requirement, URL path collision behavior, and case-sensitivity rules. Added
boomi-shared-server-info.shas a preflight script to determine whether to use a bare WSS pattern or an API Service Component. - Component search & version management — Added
boomi-component-search.shwith folder, name, type, and reference-relationship querying, stress-tested at 5,000 records (2.6 MB output). Addedboomi-version-history.shandboomi-component-diff.shfor version comparison and rollback workflows, plus aversion_management_guide.mdcovering the full versioning model. - EDIFACT support
— Full EDIFACT coverage added across EDI reference docs — delimiter defaults, composite element patterns, UNB/UNG/UNH trading partner control info, X12↔EDIFACT equivalence table, HIPAA compliance constraints, and a newedi_sap_patterns.md` guide covering IDoc structure, Z-segment extensions, and SAP partner function mapping. - Set Properties step — complete
valueTypecoverage — All 15 source value types and all 5 settable property types now documented, including date subtypes (relative,last,lastsuccessful), connector input filter attributes (elementToSetId,elementToSetName), andenforceSingleResultzero-result behavior. - And more...
We fixed these issues
- SIGPIPE crashes on large component pulls — Replaced
grep|headpipes with single-processawkextraction acrossboomi-component-pull.sh,boomi-deploy.sh, andevent-streams-setup.sh, eliminating exit 141 errors on large payloads.
Checkout April 2026 commit history
March 2026 - Versions 0.2.0 – 0.5.20
We added these features
- Branch & merge support — Full branch workflow added —
boomi-branch.sh, a--branchflag on pull/push/create scripts, branch-aware sync state, andresolve_branch_id/resolve_branch_namehelpers. Includes two new guides: a tool-oriented branch/merge guide and a runtime-verified API behavior reference. - Wave of component & step references — Six new references landed in one month: Document Cache, Cross Reference Table, Process Property, Agent step, Trading Partner (component + steps), and Disk V2 connector — all registered in the SKILL.md file index with
connectorTypeidentifiers for direct string-match discovery. - Execution query & log download — Added
boomi-execution-query.shfor querying execution records and downloading logs across all process types including WSS listeners. Added descending sort byexecutionTime. Decoupled log download fromboomi-test-execute.sh— it now returns execution ID and status only. - Full CLI rewrite to Bash
Breaking changeThis change requires updates to your configurationAll CLI tools were rewritten from Python to Bash using
curl+jq. Eliminatedrequests,PyYAML,python-dotenv, andlxmldependencies. Removed the YAML config layer — tools now source.envnatively. All documentation updated to match new invocations. - And more...
We fixed these issues
- Critical deploy bug — wrong version deployed — Rewrote
boomi-deploy.shwith a safe two-step pattern (PackagedComponent → DeployedPackage bypackageId). The previous version silently ignored branch context and deployed the globally latest version regardless of which branch was active.
Checkout March 2026 commit history
Was this topic helpful?