chore(deps): autoupdate (needs claude fix) - #28
Conversation
…onflict npm-check-updates bumped typescript to ^7.0.2, but typescript-eslint@8.65.0 (latest, incl. alphas) still requires typescript >=4.8.4 <6.1.0, so npm install failed with ERESOLVE. Held typescript back to the latest compatible stable release while keeping eslint/prettier/typescript-eslint bumps. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Autoupdate fix status: green ✅ Initial failure: `npm install` (ERESOLVE). The npm-check-updates baseline bumped `typescript` from `^6.0.3` to `^7.0.2`, but `typescript-eslint@8.65.0` (and every published alpha up to `8.65.1-alpha.7`) still declares a peer of `typescript: ">=4.8.4 <6.1.0"`. TypeScript 7.x is not yet supported by any released typescript-eslint, so the tree was unresolvable. Fix applied: pinned `typescript` back to `^6.0.3` (the latest stable release within typescript-eslint's supported peer range) in `package.json`, keeping the other autoupdate bumps (`eslint` ^10.8.0, `prettier` ^3.9.6, `typescript-eslint` ^8.65.0). Regenerated `package-lock.json` via `npm install --no-audit --no-fund`. No product logic was touched. Verified locally (clean install):
Pushed: commit `be6d80b` on `chore/autoupdate-30133639840`. |
The autoupdater's fallback path only runs `npm-check-updates -u`, so it never bumped the package version. Without a version change, release-on-version-bump does not fire on merge and the dependency updates in this PR would land on the default branch without ever being published. Bumping the patch version at the maintainer's request so the merge produces a release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PfHHX2WrotHCt9djnk6tMZ
The dependency autoupdater failed during
builds-and-checks.Run log: https://github.com/siarheidudko/objectstream/actions/runs/30133639840
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.
PR-checks will re-run on each new commit.