update

Update doraval to the latest version after installing via Homebrew, npm, or Bun.

doraval update

The command detects how doraval was installed, checks for a newer version on npm, shows a summary, and (with confirmation or --yes) runs the matching upgrade command.

Usage

doraval update [options]

Options

Flag	Description
--check	Only check for updates, do not install (Default: false)
--yes	Skip confirmation prompt (Default: false)
--via	Force install method (homebrew|npm|bun). Bypasses auto-detection and interactive picker (useful for scripts/CI)

Exact help (current):

Update doraval to the latest version (doraval update v0.2.63)

USAGE doraval update [OPTIONS]

OPTIONS

      --check    Only check for updates, do not install (Default: false)
        --yes    Skip confirmation prompt (Default: false)
  --via=<via>    Force install method (homebrew|npm|bun). Bypasses auto-detection and interactive picker (useful for scripts/CI).

Normal update flow

doraval update performs a version check against the npm registry.

• If up to date, it exits 0 with a success message.
• If an update is available, it prints current and latest versions plus a short release summary, then asks for confirmation (unless --yes).
• On confirm, it runs the detected package manager upgrade command (e.g. brew upgrade doraval).

It writes an install marker on success so future runs can detect the method reliably even if PATH changes.

Example:

doraval update

  Current: 0.2.63
  Latest:  0.2.64

  New release available.

Running: brew upgrade doraval

Successfully updated to 0.2.64.
You may need to restart your shell to pick up the new version.

--check mode

Use --check in scripts or CI to test whether an update is available without side effects.

doraval update --check

When an update exists it prints the versions and exits 1:

Update available: 0.2.63 → 0.2.64

When up to date it exits 0.

Transient installs (npx / bunx)

If you are running via npx @hacksmith/doraval or bunx @hacksmith/doraval, doraval update detects this and prints guidance instead of attempting an upgrade. Transient runs always fetch the latest on the next invocation.

Example output:

It looks like you're using doraval via npx or bunx.
These always fetch the latest version on the next run.

For easier updates, install globally:
  brew install saif-shines/tap/doraval
  npm install -g @hacksmith/doraval
  bun add -g @hacksmith/doraval

Unknown installs and --via

If detection fails and an update is available, doraval update first shows the version info, then explains and offers an interactive picker (or suggests --via for CI). --check reports availability without prompting.

doraval update

  Current: 0.2.63
  Latest:  0.2.64

  ...

✗ Could not determine how doraval was installed: ...
How was doraval installed?
  1. homebrew ...

Force a method when needed (non-interactive / scripts):

doraval update --via npm

Homebrew custom taps

When installed via a third-party tap (e.g. saif-shines/tap), Homebrew may refuse to load the formula until the tap is trusted:

Error: Refusing to load formula saif-shines/tap/doraval from untrusted tap ...
Run `brew trust --formula saif-shines/tap/doraval` or `brew trust saif-shines/tap` to trust it.

Run the suggested brew trust command once, then retry doraval update.

The update command will also suggest this in its “Common fixes” output for brew failures.

See the Installation page for the brew tap step.

How detection works

doraval uses layered detection (entrypoint path, package manager probes, then a persistent marker written on the last successful update). The marker lives under your home directory and helps after PATH or shell changes.