A fork release in Ketryx refers to creating a new version of a release that branches off from an existing baseline - such as version 1.1 - allowing you to generate release documents and conduct approvals independently of the original version's lifecycle. This action does not create a variant or duplicate of the items in the main release; instead, it enables parallel development or release paths while preserving historical context.

How to Enable a Fork Release: The option to create a fork release is located on the bottom right of the Release screen. To access this, navigate to the Versions and Releases page for your project, select the version you want to fork from. Look for the fork release option in the bottom right corner of the Release screen

Key capabilities and elements of a fork release in Ketryx include:

• Creating a new version allows you to generate fresh release documents and approve the release independently from the original baseline (e.g., version 1.1.1).
• You have the option to lock items based on their effective records at the time of this version, preventing later changes from being included. Locked items can be unlocked or converted into variants if edits are needed.
• Be aware that if newer releases already exist, their item comparisons (new/changed/removed) may be affected by changes made in this version.

In summary, a fork release enables controlled divergence from an existing release baseline without creating a new item variant, maintaining rigorous version control, auditability, and compliance.

For additional details, refer to WI-12 Variants and Versions.