release pending

Analyzes commits since the last release and outputs release decision data.

This command checks the git history and changelog to determine if there are unreleased changes that warrant a new version.

Output includes:

has_changes: whether there are releasable changes
current_version: the current released version
next_version: the calculated next version
change_counts: breakdown by change type (added, fixed, changed, etc.)

This is designed for CI/CD pipelines to determine if a release is needed.

Usage: release pending [flags] <modules>

Argument	Description
`modules`

Flag	Description
`--quiet (optional)`	Suppress output, use exit code only (0=has changes, 1=no changes)
`--all (optional)`	Check all modules with changelogs
`--published (optional)`	Check only published modules
`--internal (optional)`	Check only internal modules

Expected Output:

JSON object containing: - has_changes: boolean indicating if there are releasable changes - current_version: the current released version - next_version: the calculated next version - change_counts: breakdown by change type (added, fixed, changed, etc.)

eac release pending clie          # Check clie for pending changes
eac release pending clie --quiet  # Exit code only (0=changes, 1=no changes)
eac release pending --all         # Check all releasable modules
eac release pending --published   # Check only published modules
eac release pending --internal    # Check only internal modules

Output

JSON object containing:

has_changes -- whether there are releasable changes
current_version -- the current released version
next_version -- the calculated next version
version_type -- semver or calver
release_type -- published, internal, bundle, or none
change_summary -- breakdown by change type (added, fixed, changed, etc.)
commits_total / commits_module -- commit counts

When using --all, returns a wrapper with modules array and has_any_change flag.

release pending

Output

See Also