@lhci/cli: uuid, glob, minimatch, and js-yaml pins are multiple majors behind
@lhci/cli directly pins outdated majors of four dependencies: uuid, glob (pre-v9, deprecated per npm), minimatch, and js-yaml. This is related to but distinct from #1063 (which covers transitive inflight/rimraf deprecation warnings) and #1058 (which covers lerna/mysql2/pg-hstore/jest-image-snapshot) — neither tracks these four.
Why it matters: consumers who need current majors of any of these four for their own transitive resolution have to carry manual override/resolution pins around lighthouse-ci's own ranges, since @lhci/cli is often the only package left in the tree requiring the old majors. Affects 2 of our internal projects.
Ask: bump all four pins to their current majors in one pass. We're not aware of any lighthouse-ci behavior that depends on the old major APIs of these four — this should be a self-contained, low-risk bump even given the repo's slower release cadence.
Source: GoogleChrome/lighthouse-ci