Conversation
Greptile SummaryAdds pnpm 11-compatible Confidence Score: 5/5Safe to merge; no P0/P1 issues found and the previously flagged P1s are addressed. All previously flagged P1s (specifier/manifest mismatch, unnecessary range narrowing, sibling-dedupe only checking the first match) are addressed in this revision. Only two P2 style nits remain. No files require special attention. Important Files Changed
Reviews (4): Last reviewed commit: "fix(audit): sync partial update fixes" | Re-trigger Greptile |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 153c6eb. Configure here.

What changed
aube audit --fix=updateto update vulnerable packages through the lockfile instead of writing overrides.--fixinto pnpm's optional method form: bare--fixdefaults tooverride, and--fix=override/--fix=updateare accepted.aube audit -ito default into override fix mode, matching pnpm's interactive behavior.Why
pnpm 11 added
audit --fix=updateas the user-visible path for fixing advisories without generating override entries. Aube's previous audit fix path was override-only, so users coming from pnpm 11 got the wrong behavior.Validation
cargo check -qcargo build -qcargo clippy --all-targets -- -D warningscargo test -p aube-resolver test_pick_version_prefers_locked -- --nocapturemise run test:bats test/audit.batsNote
Medium Risk
Changes
aube auditfrom read-only to optionally rewritingpackage.jsonand the lockfile, and alters resolver version-picking behavior when vulnerable ranges are provided; this can impact dependency graphs and reproducibility if the avoidance logic is wrong.Overview
Adds pnpm-compatible audit fixing modes:
--fixnow accepts optional values (overridedefault,updateto refresh the lockfile) and introduces-i/--interactiveto select which advisories to fix.Implements
--fix=updateby re-running resolution while steering specific packages away from advisory semver ranges, then writing updatedaube-lock.yamland (when needed) adjusting direct dependency specifiers to match the new resolved versions.Extends the resolver with
vulnerable_rangessupport so sibling reuse, lockfile reuse, and version picking prefer non-vulnerable versions when available, while falling back to the original pick if no safe version exists; updates CLI docs/usage metadata and expands bats/unit tests to cover the new behaviors.Reviewed by Cursor Bugbot for commit 9a3a439. Bugbot is set up for automated code reviews on this repo. Configure here.