---
title: ForgeOps release process
description: ForgeOps release process is aimed at simplifying the management of multiple ForgeOps versions in a single branch. This process:
component: forgeops
version: 2026.2
page_id: forgeops:start:release-process
canonical_url: https://docs.pingidentity.com/forgeops/2026.2/start/release-process.html
keywords: ["Docker", "forgeops Command"]
section_ids:
  key_features: Key features
---

# ForgeOps release process

ForgeOps release process is aimed at simplifying the management of multiple ForgeOps versions in a single branch. This process:

* Removes the need to create and maintain multiple release branches for every product release.

* Enables easier upgrading and switching between multiple supported versions.

* Supports delivery of regularly promoted secure Docker images.

* Unifies documentation to easily consume product information.

## Key features

* Single `main` branch for all new releases

  * The `main` branch doesn't replace the already released forgeops branches. The currently released branches continue to be supported and updated with new minor and patch releases of the products.

  * Deployments use the latest available image for the current product version by default. Customers can select to use a specific supported image as per their needs.

* Product versions are separated from the `forgeops` repository

  * Product image tags are now maintained in tag files at <http://releases.forgeops.com>.

  * The refactored `forgeops` tool retrieves the requested tags and updates Dockerfiles/Helm/Kustomize as required.

  * All new major releases will be released using the new release process only.

  * The new process also supports 7.5 and 7.4 product image tags. Customers can continue to use the release/7.5-\* and release/7.4-\* branches until they are ready to migrate to the new process.

  * Customers can select the latest early-adapter images of the products to test the latest product features (similar to the dev image tag on the `master` branch previously).

* Supported Docker images

  * The new process is required to handle regular delivery of updated secure product images.

    * Docker images are routinely scanned for OS-level vulnerabilities and addressed by the ForgeOps team where OS patches are available.

    * The Ping Identity platform teams provide the platform-level patches.

  * The delivery process is automated, and the newly promoted tags will be available at <http://releases.forgeops.com>.

  * New `dev` branch for latest forgeops features. Equivalent to the erstwhile `master` branch which is no longer available.

  * Updated release information on <https://github.com/ForgeRock/forgeops>. Customers can get release updates by setting up their GitHub notifications.

  * Single set of documentation that is updated for ForgeOps releases and updates to the `main` branch.

  * Best efforts to document the dev branch updates similar to the early-adapter documentation.