chore(deps): autoupdate (needs claude fix) - #31
Conversation
… conflict typescript-eslint@8.66.0 (latest stable) only supports typescript <6.1.0, but the autoupdate baseline bumped typescript to ^7.0.2, causing ERESOLVE failures on npm install. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Autoupdate fix result: green ✅ Initial failure: `npm install` failed with ERESOLVE — the npm-check-updates baseline bumped `typescript` to `^7.0.2`, but `typescript-eslint@8.66.0` (latest stable, and even its newest 8.66.1-alpha prereleases) declares a peer dependency of `typescript: >=4.8.4 <6.1.0`. No published typescript-eslint version currently supports TS 7.x, so the tree was unresolvable. Fix: Pinned `typescript` down to `^6.0.3` (latest stable release still within typescript-eslint's supported peer range) in `package.json`, then regenerated `package-lock.json` via `npm install --no-audit --no-fund`. This is a devDependency-only compatibility shim — no product logic was touched. Verification (all exit 0 from a clean install):
Pushed: commit `0e50611` to `chore/autoupdate-31226390460`. |
The autoupdater bumps the version only on its success path; the npm-check-updates fallback that produced this branch does not. Without a version change, release-on-version-bump does not fire on merge and this dependency update would never be published. Automated in the workflow going forward; applied by hand here because this branch predates that change.
The dependency autoupdater failed during
builds-and-checks.Run log: https://github.com/siarheidudko/objectstream/actions/runs/31226390460
A Claude session has been dispatched to push fixes onto this branch
so the following commands all exit 0:
Claude will leave a status comment on this PR when it finishes.
The Claude workflow re-dispatches PR-checks once it is done, so the
checks below reflect its pushed fixes.