Package Version
A specific numbered release of a Salesforce managed package that can be installed in subscriber orgs, with each version potentially adding features, fixes, or changes while maintaining backward compatibility with previous versions.
Definition
A specific numbered release of a Salesforce managed package that can be installed in subscriber orgs, with each version potentially adding features, fixes, or changes while maintaining backward compatibility with previous versions.
In plain English
“A Package Version is a specific numbered release of a Salesforce managed package. Each version might add features, fix bugs, or change behavior, while ideally maintaining backward compatibility with previous versions so existing customers don't break when they upgrade.”
Worked example
Fennelford Software publishes a managed package called Inspection Suite to AppExchange. The Package's first release was Version 1.0; bug fixes shipped as 1.0.1, 1.0.2, 1.0.3 (Patch Versions); the next major feature release was Version 1.1; then 2.0 marked a breaking change requiring customer migration. Each Package Version is a specific, immutable release identified by a version number; customers see the version in their Installed Packages list and choose when to upgrade. Fennelford's release notes describe what each Package Version added or changed.
Why Package Version matters
A Package Version is a specific numbered release of a Salesforce managed package that can be installed in subscriber orgs, with each version potentially adding features, fixes, or changes while maintaining backward compatibility with previous versions. Versions typically follow semantic versioning patterns (like 2.5.1) where major version changes signal breaking changes, minor versions add features, and patch versions deliver bug fixes only.
Versioning matters significantly for ISV partners because customer orgs run different package versions and changes can break existing customer code. Well-managed packages maintain backward compatibility through deprecation patterns (marking old features as deprecated before removing them in major versions), version checks in code, and clear release notes explaining what's new in each version. Mature ISV partners treat package versioning as a core engineering discipline.
How organizations use Package Version
Maintains strict semantic versioning for their managed package, with backward compatibility guarantees for minor versions.
Documents changes in detailed release notes for every package version, helping customers plan upgrades.
Treats package version management as a core engineering discipline with formal release processes.
Trust & references
Straight from the source - Salesforce's reference material on Package Version.
- Package Versions in First-Generation Managed PackagesSalesforce Developers
Test your knowledge
Q1. What is a Package Version?
Q2. What's a common versioning scheme?
Q3. Why does backward compatibility matter?
Discussion
Loading discussion…