chore: refresh package-lock shrinkwrap metadata #251
No reviewers
Labels
No labels
bug
chore
documentation
enhancement
feature
ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
david/pi-extensions-and-skills!251
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/2026-09-15/refresh-package-lock-shrinkwrap-metadata"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
Refreshes the root
package-lock.jsonso it matches what the currently installed npm version writes.A single stale metadata flag,
"hasShrinkwrap": true, was sitting on the@earendil-works/pi-coding-agent(0.84.1) entry. That field describes a package whose published tarball contains its ownnpm-shrinkwrap.json; npm no longer emits it for this dependency, so re-resolving the lockfile drops it. Removing the stale flag keeps the lockfile canonical and stops the file showing up as a spurious working-tree modification on every install.No dependency versions, integrity hashes, or resolution URLs change — this is lockfile metadata only, with no behavioural effect on installs or runtime.
Files changed
Modified
package-lock.json— removes"hasShrinkwrap": truefrom thenode_modules/@earendil-works/pi-coding-agententry (version0.84.1). One line deleted; no other edits.Added / Deleted
None.
Verification
git diffconfirms the change is exactly one deleted line, with no version,resolved, orintegrityfields touched.lockfileVersion: 3..envfiles were included in the commit.