Skip to content

feat(cli)!: rename executable from jev to jevwise - #73

Merged
benbenbang merged 1 commit into
mainfrom
feature/25-cli-rename
Oct 9, 2026
Merged

benbenbang merged 1 commit into
mainfrom
feature/25-cli-rename

Conversation

@benbenbang

Copy link
Copy Markdown
Member

This renames the decision CLI executable and root command from jev to
jevwise, making it the identity used across builds, help output, shell
completions, and MCP guidance. No jev alias is provided, so existing
scripts and integrations that invoke jev must switch to jevwise.

Command identity:

  • Added buildinfo.CommandName as the single source for the executable
    and root-command name, now jevwise, and used it in version output,
    root command Use, and MCP background status/error messages.
  • Updated MCP background guidance to reference jevwise mcp status in
    preparing and uncertain-state errors.

Build and release:

  • Changed the make NAME to jevwise and updated CI native build and
    Windows arm64 build output names accordingly.
  • Release assets now build under the jevwise name while still
    accepting the legacy jev identity for published tags v1.0.0 through
    v1.2.0 via a LEGACY_TAGS allowlist.

Tests:

  • Added root command tests asserting the renamed identity, absence of a
    legacy jev alias, help paths, shell completion registration, and
    rejection of the old root command.
  • Added a release-assets test covering legacy-tag native identity, and
    updated buildinfo, version, and update guard tests to expect
    jevwise.

Docs:

  • Updated the README and agent onboarding guide to use jevwise, note
    the rename against releases through v1.2.0, and clarify v1.2.0 MCP PID
    and schema-2 availability.

BREAKING CHANGE: the executable and root command are renamed from jev
to jevwise with no compatibility alias; invocations must be updated.

This renames the decision CLI executable and root command from `jev` to
`jevwise`, making it the identity used across builds, help output, shell
completions, and MCP guidance. No `jev` alias is provided, so existing
scripts and integrations that invoke `jev` must switch to `jevwise`.

**Command identity:**
* Added `buildinfo.CommandName` as the single source for the executable
  and root-command name, now `jevwise`, and used it in version output,
  root command `Use`, and MCP background status/error messages.
* Updated MCP background guidance to reference `jevwise mcp status` in
  preparing and uncertain-state errors.

**Build and release:**
* Changed the make `NAME` to `jevwise` and updated CI native build and
  Windows arm64 build output names accordingly.
* Release assets now build under the `jevwise` name while still
  accepting the legacy `jev` identity for published tags v1.0.0 through
  v1.2.0 via a `LEGACY_TAGS` allowlist.

**Tests:**
* Added root command tests asserting the renamed identity, absence of a
  legacy `jev` alias, help paths, shell completion registration, and
  rejection of the old root command.
* Added a release-assets test covering legacy-tag native identity, and
  updated buildinfo, version, and update guard tests to expect
  `jevwise`.

**Docs:**
* Updated the README and agent onboarding guide to use `jevwise`, note
  the rename against releases through v1.2.0, and clarify v1.2.0 MCP PID
  and schema-2 availability.

BREAKING CHANGE: the executable and root command are renamed from `jev`
to `jevwise` with no compatibility alias; invocations must be updated.
@benbenbang
benbenbang enabled auto-merge (rebase) October 9, 2026 04:29
@github-actions github-actions Bot added documentation Improvements or additions to documentation workflows ci/cd, configs relative triage labels Oct 9, 2026
@benbenbang
benbenbang merged commit 5015c0b into main Oct 9, 2026
5 checks passed
@benbenbang
benbenbang deleted the feature/25-cli-rename branch October 9, 2026 04:30
@ptah-bw-technical-app

Copy link
Copy Markdown

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation released triage workflows ci/cd, configs relative

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant