What’s new in ForgeOps 2026.3

Release information

Highlights in 2026.3.0 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.
Helm-based secrets: You can now generate secrets using Helm in ForgeOps deployments. A Kubernetes job was created to generate an ssh key and store it in a secret. This is used by amster to connect to am.

A new subcommand, forgeops migrate sa2hs, has been added. This subcommand can be used to migrate secrets from secret agent to Helm-generated secrets.
Integration with PingOne Worker service: ForgeOps provides integration with PingOne Worker service in ForgeOps 2026.3.0 release. This allows ForgeOps users to leverage real-time risk scores for better authentication decisions.
Helm chart for RCS: A new Helm chart has been created for RCS Server. This allows users to synchronize data with a ForgeOps deployment.
Supported Ping Advanced Identity Software images: ForgeOps supports the last three major or minor versions of the Ping Advanced Identity Software images. With the availability of 8.1 images, ForgeOps supports 8.1, 8.0, and 7.5 versions of the platform images, and 7.4 images are no longer supported.

Further release information is available in the ForgeOps release notes.