Update CLI glob dependency from deprecated glob@10.5.0

[ACPK]

Node.js version

v25.8.1

NPM version

11.11.0

@checkly/cli version

checkly@7.15.0

Steps to reproduce

Install checkly@7.15.0 in an npm project:

npm install --save-dev checkly@7.15.0
npm explain glob

What is expected?

The install should not pull in deprecated glob@10.5.0 copies when the current glob release is available.

What is actually happening?

checkly@7.15.0 still declares glob: ^10.5.0, and npm explain glob shows:

glob@10.5.0 dev
node_modules/checkly/node_modules/glob
  glob@"^10.5.0" from checkly@7.15.0

glob@10.5.0 dev
node_modules/archiver-utils/node_modules/glob
  glob@"^10.0.0" from archiver-utils@5.0.2
  archiver-utils@5.0.2 from archiver@7.0.1
  archiver@7.0.1 from checkly@7.15.0

During install, npm emits:

npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version.

Any additional comments?

This looks like two dependency edges:

• direct: checkly -> glob@^10.5.0
• transitive: checkly -> archiver@7.0.1 -> archiver-utils@5.0.2 -> glob@^10.0.0

glob@13.0.6 is currently available and supports Node 18 || 20 || >=22, so it appears compatible with Checkly's current supported Node range. If the CLI can move to glob@^13, it would remove one deprecated install warning. The archiver-utils edge may require an upstream archiver/archiver-utils update or override.

[sorccu]

Hi @ACPK, we are working on a new major version which will update all dependencies to their latest versions. We are in fact hoping to release it tomorrow.

Until now the issue has been that our package still uses CommonJS which complicates use of ESM-only dependencies. Therefore we have been unable to update the glob package, among many others which themselves may use glob.