Upgrade and Migration
The documentation describes the 1.3.x release line. Check every installed @connectum/* version before applying a migration; packages can use different compatible release lines, so verify the complete set rather than inferring it from one package.
npm ls '@connectum/*'pnpm list '@connectum/*'bun pm lsCurrent Release Line
The portal may document the next release line before every package on that line is published. Use the package-specific GitHub releases and the Runtime Compatibility matrix to decide whether an upgrade applies to your installed set.
If you are upgrading from a pre-1.0 or 1.0 installation, review every applicable action below rather than assuming a direct upgrade to the documented line.
Required Actions by Starting Version
| Installed version | Required action |
|---|---|
| 1.2.x | Review the 1.3 release notes for each installed package and run your existing tests |
| 1.1.x | Review the 1.2 and 1.3 release notes for each installed package and run your existing tests |
| 1.0.x | Review package release notes; 1.1 capabilities are additive |
| RC or alpha | Follow Migrating to 1.0, then review the Service Catalog migration |
Focused Migrations
- Migrating to 1.0 — Node.js floor, explicit resilience, streaming transport validation, and removed EventBus
syncoption. - Migrating to the Service Catalog — replace legacy service registration and manual client routing.
Release History
Full release narratives, pull requests, and package-specific dependency updates belong in Connectum GitHub releases and package changelogs. This page keeps only information needed to decide and complete an upgrade.
Legacy Anchors
The following aliases preserve links published by the former combined changelog. They now route readers to the focused migration or public release history.
Continue with Migrating to 1.0 for required changes or the release history for non-actionable detail.