Patch
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 r…
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.
In plain English
“A Patch in Salesforce second-generation managed packaging is a version that delivers bug fixes to a specific major.minor version of a package without adding new features. It lets you ship targeted fixes to customers without making them upgrade to the next feature release.”
Worked example
An ISV developer at Halo Apps releases version 3.2 of their AppExchange managed package. A subscriber reports a bug where a specific picklist value breaks the record-page render. Rather than wait for the next major version, she creates a Patch version 3.2.1 that only changes the offending Apex class's null-check. The Patch can be pushed to subscribers who are on 3.2, or made available for opt-in upgrade - but it cannot introduce new features, new objects, or breaking changes. Patches ship bug fixes fast; major.minor upgrades ship features.
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
Releases patches to maintain bug fixes for customers on older versions while building new features in higher versions.
Uses patches for security fixes and critical bugs, with separate feature releases for new functionality.
Treats patch versions as part of their product support model, supporting customers across multiple versions.
Test your knowledge
Q1. What is a Patch?
Q2. Why are patches useful?
Q3. Where do patches fit in versioning?
Discussion
Loading discussion…