You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
vv pre-commit no longer blocks legitimate post-rebase commits. After git pull --rebase or a rebase against an updated base, your local branch is "diverged" from its tracking branch — both ahead and behind. The old check treated that state as "behind" and blocked the commit with an unhelpful error. pre-commit now distinguishes "purely behind" (legitimate stop — you're missing remote commits) from "diverged" (post-rebase shape — pass with an informational notice), and short-circuits the sync check entirely during a mid-flight rebase, mirroring the existing mid-merge handling. (#160)
vibe-validate works under pnpm strict isolation. The umbrella package's bin wrappers (vibe-validate, vv) used a hardcoded relative path to locate @vibe-validate/cli, which only resolves under flat-hoisted node_modules (npm classic, bun, yarn classic). Under pnpm's default strict isolation (node-linker=isolated), @vibe-validate/cli is a sibling of vibe-validate inside .pnpm/<id>/node_modules/ rather than nested, so every CLI command crashed with ERR_MODULE_NOT_FOUND. The wrappers now resolve the CLI via Node's module algorithm (createRequire), which works under every layout: npm flat, pnpm isolated, yarn berry PnP, and bun. (#161)