-
-
Notifications
You must be signed in to change notification settings - Fork 0
Refresh package metadata dependencies #1928
Copy link
Copy link
Closed
Labels
prio:lowLow priority, including the default when no higher priority is supported.Low priority, including the default when no higher priority is supported.status:confirmedConfirmed and accepted as valid work, but not yet in active implementation.Confirmed and accepted as valid work, but not yet in active implementation.type:dependenciesDependencies and upstream updates.Dependencies and upstream updates.
Description
Activity
Metadata
Metadata
Assignees
Labels
prio:lowLow priority, including the default when no higher priority is supported.Low priority, including the default when no higher priority is supported.status:confirmedConfirmed and accepted as valid work, but not yet in active implementation.Confirmed and accepted as valid work, but not yet in active implementation.type:dependenciesDependencies and upstream updates.Dependencies and upstream updates.
The local package metadata contains dependency version updates that need to be normalised into a consistent package.json and package-lock.json pair before commit. Acceptance criteria: package metadata uses repository-compliant version pins, package-lock.json matches package.json, npm test passes, and npm run check passes.