Knowledge BasePublishing
Versions and Active Version
Every publish creates a numeric version. Exactly one version is active for a project at a time, and the runtime resolves against that active pointer when it loads live tool state.
The versioning model
Version is the primary release identifier for a published pack. It gives operators a stable way to reason about what was released and what should be loaded at runtime.
This is not just a UI label. Version is part of the publish and activation model that the runtime depends on.
What active version means
Active version is the currently live pack version for a project. When the runtime checks the active pointer, this is the version it is resolving.
Only one version should be active at a time. That keeps runtime delivery clear and makes rollback or switching behavior understandable.
Why active version matters operationally
- It determines which published tool set the runtime treats as live.
- It separates draft editing work from deployed release state.
- It supports version switching to a prior validated release when operators need to change what is active.