Version History
The version history section lists all published versions of a package with their release dates, changelogs, and breaking change indicators — enabling users to select exactly the version they need.
Version List Columns
| Column | Description |
|---|---|
| Version number | Semantic version string (MAJOR.MINOR.PATCH) — latest is marked with a "Latest" badge |
| Release date | UTC date the version was published |
| Breaking changes | Red warning badge if this release contains breaking changes |
| Changelog summary | First 2-3 lines of the changelog for this version — "Show more" expands the full text |
| Install action | "Install this version" link — opens InstallHub pre-populated with this version |
Semantic Versioning Rules
| Version Bump | When to Use | Breaking Changes Marker |
|---|---|---|
| PATCH (x.y.Z) | Bug fixes only — no behavior changes | No |
| MINOR (x.Y.0) | New features, backward compatible | No |
| MAJOR (X.0.0) | Breaking changes — incompatible with previous version | Breaking |
Version Pinning
Users can install any version of a package, including older versions. Once installed, a specific version is pinned in the tenant — the tenant will not automatically upgrade to newer versions when the publisher releases them. Users must explicitly choose to upgrade.
The version history page makes it easy to see exactly what changed between versions before committing to an upgrade. Users on an older version see a banner on the package detail page: "Version 2.1.0 is installed. Version 2.3.0 is available — see changelog."
When a package has a MAJOR version bump, read the full changelog before upgrading. Breaking changes may require you to reconfigure settings, update workflow connections, or adapt forms that depend on the package. InstallHub will warn you about breaking changes in the import preview screen.
Changelog Format
Publishers should write changelogs in a structured format that gives users the information they need to decide whether to upgrade. The recommended format:
## v2.1.0 — 2026-03-15
### Added
- Added multi-currency support to the expense calculator node
- Added manager escalation when approver is unavailable for 48h
### Fixed
- Fixed incorrect tax calculation for EU-region expenses
- Fixed form validation error on the receipt upload field
### Changed
- Approval notification email template updated with new branding