Versioning

Every LPM.dev Registry release uses Semantic Versioning. A package version identifies one release and cannot be overwritten while that release exists.

Choose the next version

Semantic versions use three numbers:

MAJOR.MINOR.PATCH

Part	Increment when
MAJOR	You make an incompatible change
MINOR	You add backward-compatible functionality
PATCH	You make a backward-compatible fix

Use the LPM CLI to update the package version, then publish it:

lpm version patch
lpm publish

Replace patch with minor or major for the corresponding release. See the LPM CLI version reference for version sources, workspace behavior, and flags.

Version identity

The LPM.dev Registry rejects invalid semantic versions and atomically rejects a version that already exists for the same package. Publish a new version when release contents change.

The dashboard's short revocation window is the exception: successfully revoking a release removes its release data permanently and makes that version number available again.

How latest is selected

The LPM.dev Registry exposes the latest distribution tag. It points to the highest semantic version currently available to the consumer, not simply the most recently uploaded release.

For Pool and Marketplace packages, a version awaiting review does not replace the highest approved version. After approval, a prerelease can become latest when it is the highest available version under semantic-version ordering.

To install a specific version or range, pass it to the LPM CLI:

lpm add @lpm.dev/acme.design-system@1.4.2
lpm add @lpm.dev/acme.design-system@^1.4.0

Range	Selects
1.4.2	Exactly 1.4.2
^1.4.2	Compatible releases before 2.0.0
~1.4.2	Patch releases before 1.5.0
>=1.4.2	Any release at or above 1.4.2

The LPM CLI resolves the full dependency graph and records the selected versions in its lockfile. See Resolver and Save policy for the detailed client behavior.

Revoke a recent release

You can revoke a release from the package dashboard for 30 minutes after publication. Revocation permanently removes the release data; it is not an undoable archive or soft delete. The same version number can then be published again.

For Pool and Marketplace releases, revocation is blocked once another user or customer has accessed the release.

After the revocation window closes, publish a corrected version instead.

Deprecate a version

Deprecation adds a warning of up to 500 characters without removing the release. It is reversible: you can update or clear the warning from the package dashboard.

A deprecated version remains installable and remains eligible for latest. Use deprecation to warn consumers about a known issue or recommended replacement, not to withdraw access.

See Publishing for the LPM CLI publication workflow.