Refresh lockfile so Dependabot can resolve the adm-zip security update

[Copilot]

Dependabot’s security update job for adm-zip was failing because the repository lockfile still resolved the vulnerable 0.5.9, even though package.json already declared an override to ^0.6.0. This updates the lockfile to match the existing dependency policy so the security update is resolvable.

• Dependabot failure root cause

  • package.json already overrides adm-zip to ^0.6.0
  • package-lock.json was stale and still pinned the transitive resolution to 0.5.9
  • Dependabot interpreted that mismatch as security_update_not_possible

• Lockfile refresh

  • Re-generated package-lock.json from current package metadata
  • Updated the resolved adm-zip entry from 0.5.9 to 0.6.0
  • Synced the lockfile’s grunt-contrib-compress dependency metadata with the override-driven resolution

• Result

  • The lockfile now reflects the intended secure transitive version
  • Dependabot can evaluate the update path without treating the vulnerability fix as unresolvable

"overrides": {
  "adm-zip": "^0.6.0"
}