What’s new in ForgeOps 2026.2

Release information

Highlights in 2026.2.1 release

The main branch contains pre-release artifacts: The ForgeOps early adapter artifacts have been moved from the dev branch to the main branch of the ForgeOps repository. The main branch will be the default branch for the ForgeOps repository.

Note that the pre-release artifacts in the main branch are not meant for production use and are only meant for testing and providing feedback on the new features and changes.

The dev branch that used to contain the pre-release artifacts is discontinued and will no longer be updated.
Focus more on using Helm 4: The forgeops utility now uses Helm 4 for deploying ForgeOps on Kubernetes. Helm 4 provides improved performance and security features compared to previous Helm versions. We recommend you use Helm in ForgeOps deployments rather than Kustomize.
Security enabled by default: The forgeops utility now enables security by default for new ForgeOps deployments. Learn more in Enable security features.
SBOM for ForgeOps images: Software Bill of Materials (SBOM) is now available for ForgeOps images. SBOM provides a detailed inventory of the components and dependencies used in ForgeOps images, which can help you identify and manage security vulnerabilities and compliance issues.
Images support update: ForgeOps supports the latest available major or minor versions of the Ping Identity Platform components. Learn more at ForgeOps image support.
Further release information: Learn more about this release in the ForgeOps 2026.2.1 release notes.