mint cli updates blocked by cooldown policies

[nrynss]

We have been unable to update the mint cli for several days. Dug a little deep and found that the issue was with the mint cli's transitive dependencies being pointed to pulling the latest files. We have a cooldown period before we allow npm installations.

Mint cli dependencies have had updates in the past 24 of 30 days. So we have been unable to update for at least the last month. We can of course, make mint as an exception, but that might not be the ideal solution. Especially in large enterprises, where such exceptions follow a long process.

This is going to be the new norm in most of the enterprises going forward.

Some recommendations to Mintlify engineering:

Ship the published CLI with a committed lockfile / npm-shrinkwrap.json so installs are reproducible and don't float transitive deps to brand-new versions.

Constrain or pin fast-moving transitive deps (e.g. the @inquirer/* → chardet chain), and/or offer a release channel that lags the newest transitive versions.

Given ~2 releases/day, this will recur for any customer behind a min-release-age firewall with products like Endor Labs Package Firewall.