Application Versioning enables development teams to create and manage multiple versions of an Unqork application. Each new application version automatically captures a complete snapshot of its configuration, creating a robust version history with significant benefits for development teams.
The benefits include the following:
Parallel Workflows: Teams can work in separate branches of the same application. This prevents their changes from affecting what other team members are working on.
Version Rollback Security: Revert to a previous version. If a recent change causes issues, Creators can rollback to a stable application version. Doing so ensures smooth operation and allows for the flexible testing of new features that can be quickly withdrawn if undesirable.
Release Control: Decide when and what parts of an application and its dependencies are published. Control application and dependency promotions to other environments.
Improved Governance: Increase transparency, accountability, and control throughout the entire lifecycle of an application. Enables version changes to be distinct, measurable, and auditable events.
Because this feature represents a significant change in how your team works in Unqork, it’s important to understand the full considerations for employing Application Versioning before applying it.
Discover if Application Versioning is right for your team in our Evaluating Application Versioning for Unqork Creators article.
Core Features of Unqork Application Versioning
Below are the core features of Unqork Application Versioning, along with a description of when to use them in your application:
Key Features | Description | Supported Elements |
|---|---|---|
Manage direct and transitive dependencies between application versions to ensure that components work together and the application remains stable and functional as updates are made. |
| |
| ||
| ||
| ||
|
Learn all about Application Versioning by reviewing our Getting Started With Unqork's Application Versioning article.