pcpm outdated

pcpm outdated [options]

pcpm outdated queries the feed for every direct dependency in CPM and reports the bump type relative to the version you have pinned.

Columns

Column	Meaning
Package	The package id.
Current	The version pinned in Directory.Packages.props.
Latest	The highest stable version on the feed.
Bump	major, minor, patch, or prerelease.

Options

Flag	Effect
--direct	Only check direct dependencies (default).
--all	Check every package in the lockfile, including transitive.
--prerelease	Include pre-release versions in the search.
--json	Output as JSON.
--write	Update Directory.Packages.props to the latest version.

Examples

# Quick sanity check
pcpm outdated

# See what's on offer across the whole graph
pcpm outdated --all

# Bump everything (review the diff before committing)
pcpm outdated --write

Bump types

pcpm outdated uses NuGet.Versioning to compute the version distance:

• major — leftmost non-zero component changed.
• minor — second component changed, major is the same.
• patch — third component changed, major and minor are the same.
• prerelease — same X.Y.Z but with a pre-release tag, or a different pre-release tag.

These are the same heuristics that dotnet outdated and Dependabot use, so PCPM’s “major” matches everyone else’s.

See also

• Configuration — for floating versions.