feat(pnpm): catch up with pnpm 11 parity#761
Conversation
Greptile SummaryThis PR adds pnpm 11 lockfile parity across several dimensions:
Confidence Score: 5/5Safe to merge; the lockfile read/write paths have comprehensive new tests and the changes are well-contained. The gitHosted flag is correctly threaded through all three LockedPackage shapes (Git, RemoteTarball, registry-keyed), dep-path rekeys propagate to DirectDep references, and the codeload integrity sidecar mechanism ensures warm-cache re-runs emit consistent lockfiles. Each behavioral change is backed by a dedicated round-trip test. The audit and publish changes are straightforward and similarly tested. The new fuzzy git-resolution matching in Important Files Changed
Reviews (10): Last reviewed commit: "fix(lockfile): guard git metadata fallba..." | Re-trigger Greptile |
jdx
left a comment
There was a problem hiding this comment.
Addressed the remaining summary feedback: 923a200 makes recursive --json emit the single-object shape when exactly one workspace package is selected, while keeping arrays for true multi-package fanout, and updates the generated CLI help to call out the multi-package array case.
This comment was generated by Codex.
|
Also addressed Greptile's minor note in This comment was generated by Codex. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 05b69ab. Configure here.
|
Addressed Greptile feedback in 0e86bad: pnpm This comment was generated by Codex. |

Summary
auditConfig.ignoreGhsas/ignoreCvesand align publish JSON output with npm/pnpm shapeNPM_ID_TOKENfor publish provenance detectionValidation
cargo fmt --checkcargo checkcargo test -p aube-lockfile writer_cargo test -p aube configured_audit_ignores_reads_ghsa_and_legacy_cve_keyscargo test -p aube publish_json_single_uses_npm_compatible_object_shapecargo clippy --all-targets -- -D warningsThis PR was generated by Codex.
Note
Medium Risk
Lockfile parse/write and resolver/git integrity paths affect installs and third-party pnpm lockfiles; publish JSON shape is a breaking change for consumers expecting a one-element array.
Overview
This PR brings pnpm 11 lockfile parity and several CLI/registry behaviors in line with npm/pnpm.
Lockfile (
aube-lockfile) addsgitHosted/registry_git_hosted, preserves non-derivable registry tarball URLs (e.g. GitHub Packages), and improves git resolution round-trips viagit_commits_match, importerdep_pathrekeys, and fuller commit hashes from dep-path keys. Resolver/store reuse codeload cache integrity sidecars, carry git integrity into locked packages, and centralize SHA-512 inaube-store(dropsbase64fromaube-resolver).CLI:
auditmergesauditConfig.ignoreGhsas/ignoreCveswith--ignore;publish --jsonemits a single npm-shaped object (array only for multi-package publishes) withid,shasum,integrity,unpackedSize, etc.; provenance acceptsNPM_ID_TOKEN; pack tracksunpacked_sizefor that JSON.Reviewed by Cursor Bugbot for commit 0e86bad. Bugbot is set up for automated code reviews on this repo. Configure here.