End-of-life announcement: Comply (SCM) version 2.x 

6 views
Skip to first unread message

Puppet Product Updates

unread,
Aug 5, 2025, 5:17:32 PMAug 5
to
:puppet-logo-dag-2025: End-of-life announcement: Comply (SCM) version 2.x 
Puppet by Perforce announces the end of life (EOL) for Comply 2.x, the legacy version of Security Compliance Management (SCM), effective February 5, 2026—six months from the date of this notice. Going forward, development will focus on the latest version, SCM 3.x, which will continue to receive full support, updates, and enhancements. 
Next steps 
  • Migration to SCM 3.x 
If your organization is currently using Comply (SCM) 2.x, we recommend migrating to SCM 3.x as soon as possible to avoid disruption and ensure continued support. Migrating to SCM 3.x reduces dependency on external applications, improving efficiency and reliability, while retaining or enhancing all core features. 
  • Active maintenance period 
In the six-month period between this announcement and the EOL date, quarterly releases of Comply (SCM) 2.x will address critical bugs and security issues, and we'll provide support for customers transitioning to SCM 3.x. 
  • Extended maintenance option 
Customers who require more time to complete their migration may opt into an additional six months of extended support for Comply (SCM) 2.x, available as a premium offering. Please contact your account team for more information. 
  • End of support 
After the extended support period ends, no further updates, fixes or support will be provided for Comply (SCM) 2.x. We strongly encourage planning your migration in advance to avoid disruption. 
We’re here to help 
Our Professional Services, Support, and Engineering teams are available to assist with migration planning, technical questions, and any challenges you may encounter during this transition. 


This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.


Reply all
Reply to author
Forward
0 new messages