Definition
In Salesforce second-generation managed packaging, a patch version that delivers bug fixes to a specific major.minor version of a package without introducing new features, allowing subscribers to receive targeted fixes.
Real-World Example
Consider a scenario where a Salesforce developer at CodeBridge is working with Patch to create a robust integration between Salesforce and an external system. Using Patch, the developer builds an efficient solution that syncs data in near real-time, handles error scenarios gracefully, and includes detailed logging for troubleshooting.
Why Patch Matters
In Salesforce second-generation managed packaging, a Patch is a version that delivers bug fixes to a specific major.minor version of a package without introducing new features, allowing subscribers to receive targeted fixes. Patches are useful when customers need a fix but aren't ready to take the latest version with all its new features. The patch maintains the same major.minor version while incrementing the patch number (like 2.5.1 -> 2.5.2).
Patch versions are part of mature ISV practice for supporting multiple customer versions. Without patches, customers stuck on older versions either can't get fixes or have to upgrade to the latest version (which may include unwanted changes). With patches, ISV partners can support older versions with bug fixes while customers move to new feature versions on their own schedule. Salesforce DX and second-generation packaging provide better patch capabilities than the older first-generation packaging.
How Organizations Use Patch
- •Quantum Labs — Releases patches to maintain bug fixes for customers on older versions while building new features in higher versions.
- •TerraForm Tech — Uses patches for security fixes and critical bugs, with separate feature releases for new functionality.
- •CodeBridge — Treats patch versions as part of their product support model, supporting customers across multiple versions.