@eclipse-docks/cli

Developer CLI for apps built on Eclipse Docks.

Usage

npx @eclipse-docks/cli release                       # bump patch, prompt for release notes
npx @eclipse-docks/cli release minor                 # bump minor
npx @eclipse-docks/cli release major -m "notes"      # bump major with inline release notes
npx @eclipse-docks/cli release v1.2.3                # explicit version
npx @eclipse-docks/cli release --since v1.2.0        # notes from commits since that tag
npx @eclipse-docks/cli release --dry-run             # print what would be tagged
npx @eclipse-docks/cli release --no-push             # create the tag locally without pushing

release

Creates an annotated tag whose name is the version (vX.Y.Z) and pushes it. When pushing (the default), any unpushed commits on the current branch are pushed to origin first. The tag message body becomes the GitHub Release notes.

Wire release in CI with .github/workflows/app-release.yml: downstream apps usually trigger it on v* tag push; this monorepo waits for a green CI run on main first (see .github/workflows/release.yml). If CI fails after the tag was pushed, that workflow deletes the orphan remote tag so GitHub Release history has no gaps. Remove the local tag before retrying: git tag -d vX.Y.Z.

The last version is the most recent vX.Y.Z tag reachable from HEAD (via git describe), not the highest semver tag in the repository. That drives the default bump and changelog range.

If no release notes are given via -m, an end-user-facing summary is generated from the commits since that tag (or since --since vX.Y.Z when set), grouped under Features, Fixes, Docs, and Chore/Refactor, and offered as the default (press Enter on an empty first line to accept it).