You’ve probably seen Salesforce’s Product and Feature Retirement Newsletter that gets emailed every once in a while.
The item that catches my attention the most is when Salesforce retires platform API versions. For example, the most recent newsletter says API versions 31 to 40 will be deprecated in June, 2028.
If you’re not a developer, you may not understand the implications. Basically anytime you build a flow, apex class, trigger, Visualforce page, etc., it’s stamped with an API version. This version is usually the most recent version at the moment of creation. Right now, it’s 67.
By stamping the component’s version, it’s frozen in time. This allows the component to continue functioning while the version keeps increasing.
For security reasons, Salesforce retires old versions. This means that every several years, you need to ensure all components in your org are not on the deprecated list, or they will cease to work.
But actually….
Retirement does not impact the components mentioned above. It only impacts SOAP, REST, and Bulk API versions.
PS. This means those old NPSP components are safe 🙂
The takeaway
While it’s a good practice to keep your components’s API version relatively recent, it’s not a make-or-break situation.
You can read the full article for Sept 2026