chore(deps): weekly CLI dependency update (2026-08-31) [RED-895] [ship]

[sorccu]

Linear: RED-895

Weekly dependency update. Every package moves to the newest version that is both installable on our minimum supported Node (20.19.0, from engines.node) and past pnpm's 2-day minimumReleaseAge embargo.

Updated

Package	Type	Owner	From → To
eslint	devDependency	root	10.9.0 → 10.9.1
simple-git-hooks	devDependency	root	2.13.1 → 2.14.0
typescript-eslint	devDependency	root	8.67.0 → 8.68.0
@oclif/plugin-help	dependency	checkly, create-checkly	6.2.58 → 6.3.0
@oclif/plugin-warn-if-update-available	dependency	checkly, create-checkly	3.1.73 → 3.2.0
@typescript-eslint/typescript-estree	dependency	checkly	8.67.0 → 8.68.0
axios	dependency	checkly, create-checkly	1.19.0 → 1.20.0
oclif	devDependency	checkly	4.23.30 → 4.24.0

The only other lockfile movement is @oclif/plugin-not-found 3.2.88 → 3.3.0, pulled in transitively by oclif 4.24.0 — also floor-compatible and past the embargo.

Held back

Node floor — the newest major of each of these requires a Node newer than 20.19.0, so they stay put: @commitlint/cli and @commitlint/config-conventional at 20.5.3 (21.2.2 needs >=22.12.0), chalk at 5.6.2 (6.0.0 needs >=22), execa at 9.6.1 (10.0.1 needs >=22), lint-staged at 16.4.0 (17.4.1 needs >=22.22.1), nanoid at 5.1.16 (6.0.1 needs ^22 || ^24 || >=26), recast at 0.23.21 (0.24.0 needs >=22).

No explicit pins were added for them. pnpm update --latest only touches packages named on the command line, and none of these was named — so their ranges are untouched rather than rewritten.

Peer range — typescript stays at 6.0.3 (newest 7.0.2) because typescript-eslint@8.68.0 declares peerDependencies.typescript: ">=4.8.4 <6.1.0". TypeScript 7 is unavailable until that widens.

Policy — @types/node stays on 22.x so the types track our minimum supported Node rather than the newest, and vitest stays on 3.x until the known 4.x incompatibilities are resolved.

Verification

Build, pnpm run prepack, pnpm lint, commitlint accept/reject smokes, 2680 checkly unit tests, 19 create-checkly unit tests, no skills/ drift, pnpm install --frozen-lockfile clean, and an engines.node re-read confirming all eight landed versions admit Node 20.19.0. No engine or peer warnings during install.

Not verified: pnpm-workspace.yaml's trustPolicy: no-downgrade is a pnpm 11 pre-install check, and pnpm 11 requires Node >=22.13. Resolution ran on pnpm 10, which is what CI pins as well, so this matches the pipeline's own coverage.

Note on the @oclif/plugin-help bump

While smoke-testing the help paths I found that packages/cli/src/commands/help.ts defines our own help command, which shadows the one @oclif/plugin-help contributes — Config.load resolves findCommand('help') to plugin=checkly strict=true args=[], not the plugin's strict=false args=[command]. The helpClass is ours too. So the plugin is loaded and then never invoked, and this bump is inert beyond plugin loading.

A consequence worth a separate ticket: checkly help <topic> (e.g. checkly help env) fails with help:env is not a checkly command, because our help takes no positional argument. That is pre-existing behaviour, unrelated to this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FnHLUKRbRecW2cDZEiamoE

[github-actions]

Auto-approved: ship/show PR from a same-repo branch.