Package Version
An immutable, uniquely numbered build of a 2GP package, the unit every install and upgrade is based on.
Definition
A package version is a single, immutable build of a 2GP package (managed or unlocked), created with sf package version create from a Dev Hub and identified by a four-part number: major, minor, patch, and build. Once created, a version's metadata can't change; a new version is required for any further edits, which is what makes upgrade paths predictable. Every version starts in Beta status, installable only for testing, and moves to Released through promotion before it can go to production or be depended on by other packages. Subscriber orgs install a specific version and can later upgrade to a newer one, with Salesforce validating the upgrade path against declared ancestry. Our guide to second-generation packaging covers the full version lifecycle.
How it works in Serpent
Serpent creates and promotes package versions automatically as tasks complete, without requiring anyone to run CLI version-create commands or track version numbers in a spreadsheet. Dependency-aware version bumps, ancestry, and promotion between Beta and Released happen through the pipeline, and subscriber org tracking shows exactly which version each customer runs. See 2GP CI/CD in Serpent for the full versioning workflow.
Package Version, answered
Start free. No credit card, no install, no commitment.
Set up in under 15 minutes. No DevOps hire needed.