Hello Incorta Community,
We're writing to share an important change in how we name and number Incorta releases. Starting with our upcoming release, referred to as 8.0.0 (2026.8), Incorta is adopting semantic versioning as the foundation of its release naming. This aligns Incorta with a widely used, industry-standard versioning model that communicates the nature and compatibility of each release directly through the version number itself.
This post explains what is changing, how to read the new version numbers, and what it means for you.
What is changing
Previously, Incorta releases were identified using a calendar-based scheme (for example, 2026.3.0, followed by service packs such as 2026.3.1 through 2026.3.6). While this told you when a release arrived, it did not clearly communicate the scope or compatibility of the changes it contained.
Going forward, releases will carry a semantic version. The first release under the new convention is:
8.0.0-2026.8
For this release, we are sharing the old convention and new convention in a single version name to indicate a temporary bridge between the two release naming conventions.
This release builds on all features previously introduced in the 2026.3.0 release and its service packs through 2026.3.7.
How to read the new version number
Going forward, releases use a three-part semantic version in the form:
vMAJOR.MINOR.PATCH — for example, v8.0.1
| Version part |
What it means |
| MAJOR |
Backward-incompatible changes that may require action from users |
| MINOR |
New, non-breaking feature additions, improvements, and bug fixes |
| PATCH |
Bug fixes and small corrections |
In simple terms, the version number now gives you a clearer first indication of a release's impact before you review the full release notes.
A note on this release: 8.0.0 and 2026.8
This release sits at the transition point between our old and new conventions, so you will see it referred to in two ways: 8.0.0 (the new semantic version) and 2026.8 (the calendar reference from our previous convention). We are intentionally using both to bridge between the old and new naming, making it easy to connect this release to what came before while introducing the semantic version. Going forward, the release increments will be added to the semantic version while the calendar reference remains static (e.g. 8.6.2-2026.8).
Why we're making this change
Semantic versioning is a well-established standard across the software industry. Adopting it gives you a clearer, more predictable way to understand each release before you plan an upgrade:
- Clearer communication. Version numbers better reflect whether a release contains fixes, new features, or backward-incompatible changes.
- More frequent releases. Non-breaking features can now be delivered on top of an existing released version throughout the year, rather than waiting for the next large release.
- Industry alignment. If your teams already work with semantically versioned tools and platforms, Incorta releases now follow the same familiar logic.
As a general guideline:
- Patch releases should usually require the least validation effort; a guaranteed scope of fixes only.
- Minor releases may introduce meaningful new capabilities while preserving compatibility.
- Major releases should be reviewed carefully for migration and adoption planning.
What this change does not replace
This update improves how we name and communicate releases. It does not replace the need for release notes, upgrade guidance, or standard validation practices. Version numbers indicate the general level of impact, but release notes remain the source of truth for exact changes, technical details, and implementation guidance.
What this means for you
No action is required simply because of the naming change itself. This is a change to how releases are named and numbered, not a change to your existing environment.
Please note: the 8.0.0 (26.8) release includes major platform and runtime updates. As always, review the full release notes and upgrade guidance before upgrading. In particular, a MAJOR version is your signal to check for prerequisites and compatibility notes ahead of time.
Documentation and communications will reference the new version format going forward. When you see a semantic version such as v8.0.1, you'll now be able to interpret it using the guidance above.
Questions?
If you have questions about the new versioning convention or how it affects your upgrade planning, reply to this post and our team will be glad to help. We'll continue to share details as the 8.0.0-2026.8 release becomes available, including full release notes and upgrade documentation.
Thank you, as always, for being part of the Incorta Community.
The Incorta Team
.png "Community Manager"){kind=icon}
