You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protected files were modified in this change.
This pull request is in request-review mode and requires explicit human scrutiny before merge.
Protected files: package-lock.json, package.json
Dependency Release Train Summary
What changed
Package/ecosystem: npm (root)
Manifest(s): package.json, package-lock.json
Old version → New version:
eslint: 10.9.1 → 10.10.0
@typescript-eslint/eslint-plugin: 8.67.0 → 8.70.0
@typescript-eslint/parser: 8.67.0 → 8.70.0
typescript-eslint: 8.67.0 → 8.70.0
@types/node: ^25.9.5 → ^25.9.6
Update type: patch/minor (no majors)
Why now
Routine freshness bump. No open Dependabot PRs, no open security advisories/alerts
on this repo at time of this run. This closure was previously identified as the
next coherent freshness bundle in prior cache-memory runs but does not appear to
have landed on main yet (current main still pins the old versions), so it is
re-submitted here.
Risk assessment
Runtime/dev/build/CI scope: dev-only (lint/typecheck tooling + Node type defs);
does not affect the production dist/cli.js runtime bundle or container images.
Direct/transitive: all five are direct devDependencies in the root package.json.
Reachability: used via eslint.config.mjs (flat config) and tsconfig*.json
during npm run lint / npm run type-check / CI; no application source changes
needed.
These four packages (eslint, typescript-eslint, @typescript-eslint/eslint-plugin, @typescript-eslint/parser) are bundled together as one atomic closure because
they share a single ESLint flat-config resolver invocation and must stay
version-aligned; @types/node is a small unrelated patch-only bump riding along
in the same manifest (zero additional risk).
Peer dependency compatibility verified before bumping: @typescript-eslint/eslint-plugin@8.70.0
requires @typescript-eslint/parser: ^8.70.0 (satisfied) and eslint: ^8.57.0 || ^9.0.0 || ^10.0.0 (satisfied by eslint@10.10.0) and typescript: >=4.8.4 <6.1.0 (repo pins typescript: ^5.9.3, unchanged, satisfied).
Validation
Commands run:
npm install --package-lock-only --registry=https://registry.npmjs.org/ --legacy-peer-deps — succeeded, regenerated package-lock.json cleanly (repo's own .npmrc points at an internal registry unreachable from this sandbox; public registry used for read-only resolution only).
npm audit --package-lock-only --registry=https://registry.npmjs.org/ — 0 vulnerabilities, both before and after.
npm outdated --registry=https://registry.npmjs.org/ — confirms all five targeted packages now resolve to their intended wanted/latest versions.
JSON validity check (python3 -m json.load) on both package.json and package-lock.json — OK.
Partial npm install --ignore-scripts (killed after the sandbox's documented npm-stall limitation) had already resolved and installed all five target packages into node_modules before being interrupted; spot-checked each package's own node_modules/*/package.json"version" field to confirm eslint@10.10.0, typescript-eslint@8.70.0, @typescript-eslint/{eslint-plugin,parser}@8.70.0, and @types/node@25.9.6 all resolve/install correctly.
Result: lockfile-only resolution and audit both clean; version bumps confirmed installable.
Remaining gaps: could not run npm run lint / npm run type-check / npm test to completion — full npm install/npm ci against the public registry reliably stalls in this sandbox (this repo's internal registry is unreachable here). CI is the source of truth for lint/typecheck/test signal on this PR.
None — dev-tooling only (linting/type-checking), no auth/crypto/payment/DB/serialization/telemetry/CI-runner/container-base changes.
Breaking-change notes
None (no major version bumps).
Reviewer checklist
CI passes
CODEOWNERS or service owners reviewed
Security-sensitive areas approved, if applicable
Deployment/canary owner confirms runtime health, if needed
Rollback guidance
Revert this PR, or manually pin eslint back to 10.9.1, @typescript-eslint/eslint-plugin/@typescript-eslint/parser/typescript-eslint back to 8.67.0, and @types/node back to ^25.9.5 in package.json, then regenerate package-lock.json.
package.json and package-lock.json must be reverted together.
Smart-Dependabot-Merge-Candidate: yes
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Caution
Protected files were modified in this change.
This pull request is in
request-reviewmode and requires explicit human scrutiny before merge.Protected files:
package-lock.json,package.jsonDependency Release Train Summary
What changed
package.json,package-lock.jsoneslint:10.9.1→10.10.0@typescript-eslint/eslint-plugin:8.67.0→8.70.0@typescript-eslint/parser:8.67.0→8.70.0typescript-eslint:8.67.0→8.70.0@types/node:^25.9.5→^25.9.6Why now
on this repo at time of this run. This closure was previously identified as the
next coherent freshness bundle in prior cache-memory runs but does not appear to
have landed on
mainyet (currentmainstill pins the old versions), so it isre-submitted here.
Risk assessment
does not affect the production
dist/cli.jsruntime bundle or container images.devDependenciesin the rootpackage.json.eslint.config.mjs(flat config) andtsconfig*.jsonduring
npm run lint/npm run type-check/ CI; no application source changesneeded.
eslint,typescript-eslint,@typescript-eslint/eslint-plugin,@typescript-eslint/parser) are bundled together as one atomic closure becausethey share a single ESLint flat-config resolver invocation and must stay
version-aligned;
@types/nodeis a small unrelated patch-only bump riding alongin the same manifest (zero additional risk).
@typescript-eslint/eslint-plugin@8.70.0requires
@typescript-eslint/parser: ^8.70.0(satisfied) andeslint: ^8.57.0 || ^9.0.0 || ^10.0.0(satisfied byeslint@10.10.0) andtypescript: >=4.8.4 <6.1.0(repo pinstypescript: ^5.9.3, unchanged, satisfied).Validation
npm install --package-lock-only --registry=https://registry.npmjs.org/ --legacy-peer-deps— succeeded, regeneratedpackage-lock.jsoncleanly (repo's own.npmrcpoints at an internal registry unreachable from this sandbox; public registry used for read-only resolution only).npm audit --package-lock-only --registry=https://registry.npmjs.org/— 0 vulnerabilities, both before and after.npm outdated --registry=https://registry.npmjs.org/— confirms all five targeted packages now resolve to their intendedwanted/latestversions.python3 -m json.load) on bothpackage.jsonandpackage-lock.json— OK.git diff --stat— exactly 2 files changed (package.json,package-lock.json), zero unrelated churn.npm install --ignore-scripts(killed after the sandbox's documented npm-stall limitation) had already resolved and installed all five target packages intonode_modulesbefore being interrupted; spot-checked each package's ownnode_modules/*/package.json"version"field to confirmeslint@10.10.0,typescript-eslint@8.70.0,@typescript-eslint/{eslint-plugin,parser}@8.70.0, and@types/node@25.9.6all resolve/install correctly.npm run lint/npm run type-check/npm testto completion — fullnpm install/npm ciagainst the public registry reliably stalls in this sandbox (this repo's internal registry is unreachable here). CI is the source of truth for lint/typecheck/test signal on this PR.Control Plane
Sensitive surface area
Breaking-change notes
Reviewer checklist
Rollback guidance
eslintback to10.9.1,@typescript-eslint/eslint-plugin/@typescript-eslint/parser/typescript-eslintback to8.67.0, and@types/nodeback to^25.9.5inpackage.json, then regeneratepackage-lock.json.package.jsonandpackage-lock.jsonmust be reverted together.Smart-Dependabot-Merge-Candidate: yes
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.Create the pull request manually
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Add this agentic workflow to your repo
To install this agentic workflow, run