Patch Version
The third number in a package version, reserved for fixes shipped off an already-released version without a full new release.
Definition
The patch version is the third number in a package's major.minor.patch.build scheme, reserved for fixing a bug in an already-released version without incrementing major or minor and without changing the metadata surface. For managed packages, creating a patch requires going through Salesforce Support's patch org process, since it operates on a version subscribers already have installed; unlocked packages can create a patch version directly with the CLI like any other version. Patches exist because a full minor release, with its own testing cycle and gradual rollout, is often too slow for an urgent fix that subscriber orgs are actively blocked by. Overusing patches for anything beyond narrow bug fixes is a common anti-pattern, since patches skip some of the review a minor version gets. See our guide to second-generation packaging for the full versioning scheme.
How it works in Serpent
Serpent supports patch version creation for unlocked packages directly through the pipeline, and tracks the managed package patch process alongside a team's regular release history so a patch is never a step outside the normal workflow. Subscriber org tracking shows exactly which orgs are still on the pre-patch version so a hotfix rollout can be monitored to completion. See 2GP CI/CD in Serpent for how patch versions fit alongside regular releases.
Patch Version, answered
Start free. No credit card, no install, no commitment.
Set up in under 15 minutes. No DevOps hire needed.