chore(deps): weekly CLI dependency update (2026-09-08) [RED-921] [ship] - #1477
Merged
Merged
Conversation
Bump every dependency to the newest version that is both installable on our minimum supported Node (22.13.0, from engines.node) and past pnpm's 2-day minimumReleaseAge embargo. Updated: eslint 10.9.1 -> 10.10.0 (root, devDep) globals 17.11.0 -> 17.12.0 (root, devDep) typescript-eslint 8.68.0 -> 8.69.0 (root, devDep) @oclif/core 4.14.0 -> 5.0.0 (both, dep) @oclif/plugin-help 6.3.0 -> 7.0.0 (both, dep) @oclif/plugin-warn-if-update-available 3.2.0 -> 4.0.0 (both, dep) @typescript-eslint/typescript-estree 8.68.0 -> 8.69.0 (checkly, dep) ast-types 0.16.1 -> 0.16.3 (checkly, dep) @playwright/test 1.62.1 -> 1.63.0 (checkly, devDep) oclif 4.24.0 -> 5.0.1 (checkly, devDep) The four oclif packages move together as a major: plugin-help 7, plugin-warn 4 and oclif 5 all require @oclif/core ^5, so bumping them as a set keeps a single copy of core in the tree. The only breaking change in all four is engines.node >=22.0.0, which our floor already satisfies; @oclif/core 4.14.0 -> 5.0.0 contains no source changes, and oclif 5.0.1 only touches src/commands/manifest.ts cosmetically (type-only imports). Held back because the newest major raises the Node floor: lint-staged stays at 16.4.0 (every 17.x needs >=22.22.1). No explicit pin was added: `pnpm update --latest` only touches packages named on the command line. Held back by a peer range: typescript stays at 6.0.3 (newest 7.0.2) because typescript-eslint@8.69.0 declares peerDependencies.typescript ">=4.8.4 <6.1.0". Not eligible yet (inside the embargo, re-evaluate next run): typescript-eslint and @typescript-eslint/typescript-estree 8.70.0 (published 2026-09-07). Excluded by 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 (newest is now 5.0.0) until the known 4.x incompatibilities are resolved. Verified: build (both packages incl. ai-context), `pnpm run sync:skills` with no skills drift, `oclif manifest` via `pnpm pack`, `pnpm lint`, commitlint accept/reject, 2935 checkly unit tests, 48 create-checkly unit tests, `pnpm install --frozen-lockfile` clean, and an engines.node re-read confirming all ten landed versions admit Node 22.13.0. No engine or peer warnings. Resolution ran on pnpm 10.33.4, the version CI pins. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sorccu
changed the title
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear: RED-921
Bump every direct dependency to the newest version that is both installable on our minimum supported Node (22.13.0, from
engines.node) and past pnpm's 2-dayminimumReleaseAgeembargo.Updated
The four oclif packages move together as a major: plugin-help 7, plugin-warn 4 and oclif 5 all require
@oclif/core ^5, so bumping them as a set keeps a single copy of core in the tree. The only breaking change in all four isengines.node >=22.0.0, which our floor already satisfies.@oclif/core4.14.0 → 5.0.0 contains no source changes; oclif 5.0.1 only touchessrc/commands/manifest.tscosmetically.Held back
peerDependencies.typescript ">=4.8.4 <6.1.0".Not eligible yet (inside the embargo, re-evaluate next week)
Excluded by policy
Verification
Run in the worktree on pnpm 10.33.4 (the version CI pins): both packages build including the AI context,
pnpm run sync:skillsshows no skills drift,oclif manifestran under oclif 5 viapnpm pack,pnpm lintpasses, commitlint accepts a valid header and rejects an invalid one, 2935 checkly and 48 create-checkly unit tests pass,pnpm install --frozen-lockfileis clean, and every landed version'sengines.nodeadmits 22.13.0. No engine or peer warnings.🤖 Generated with Claude Code