Skip to content

fix(docs): use verda --version instead of non-existent verda version#50

Merged
hi-lei merged 1 commit into
mainfrom
fix/version-command-docs
Jun 2, 2026
Merged

fix(docs): use verda --version instead of non-existent verda version#50
hi-lei merged 1 commit into
mainfrom
fix/version-command-docs

Conversation

@hi-lei
Copy link
Copy Markdown
Collaborator

@hi-lei hi-lei commented Jun 2, 2026

Summary

verda version is not a command — cobra returns unknown command "version" and exits 1. Two places used it:

  • README.md — the "verify installation" line under Verify & update.
  • test/test-release-packages.sh (5×) — post-install smoke tests run <install> && verda version, so the && verda version would have failed every package check (deb / rpm / apk / tar.gz / homebrew) on the non-zero exit. This is a latent bug in the release verification pipeline.

Both now use verda --version. No other file referenced verda version (no Go code, completions, or other docs).

Testing

  • grep -rn "verda version" across the repo → zero remaining occurrences.
  • Pre-commit hooks passed (no Go files touched).

🤖 Generated with Claude Code

`verda version` is not a command (cobra returns "unknown command", exit 1).
Correct the README "verify installation" line and the five post-install
smoke tests in test/test-release-packages.sh, where `<install> && verda
version` would have failed every package check (deb/rpm/apk/tar.gz/homebrew)
on a non-zero exit.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@hi-lei hi-lei merged commit 24c701a into main Jun 2, 2026
12 checks passed
@hi-lei hi-lei deleted the fix/version-command-docs branch June 2, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant