chore(deps-dev): Bump @eslint/js from 9.39.4 to 10.0.1 - #263
Conversation
Bumps [@eslint/js](https://github.com/eslint/eslint/tree/HEAD/packages/js) from 9.39.4 to 10.0.1. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/commits/v10.0.1/packages/js) --- updated-dependencies: - dependency-name: "@eslint/js" dependency-version: 10.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
…rn/eslint/js-10.0.1
The bump was red because eslint 10's recommended set adds
`preserve-caught-error` and `no-useless-assignment`, and nine existing
sites break them. Both findings are real, so they are fixed rather than
silenced.
preserve-caught-error (5) — settings loading (twice), the directory
trust store, the hook trust file, and the MCP `headersHelper` each
wrapped a caught error in a new Error carrying only `.message`. A
JSON parse failure or a spawn error therefore arrived with its stack,
`errno` and `path` gone: the message says "Failed to parse ~/.deepcode/
settings.json: Unexpected token" and nothing says which byte, or that
the real failure was EACCES. Each now passes `{ cause }`.
no-useless-assignment (4) — `patch`/`binary` in workspace-diff and
`stdout` in the Grep tool were initialised and then overwritten on every
path that reads them; the initialisers only suppressed TypeScript's
definite-assignment analysis. Dropping them lets tsc prove what the
initialiser was papering over, and it does. In `parseQName` the `pos++`
before `break` consumed the DNS root label for a variable nothing reads
after the loop.
Note eslint itself was already 10.8.0 in the lockfile — only `@eslint/js`
was pinned at 9, so the repo was running a v10 engine against a v9
recommended config. This closes that gap.
typecheck, lint, format, docs clean; 1671 tests pass, 19 skipped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Reviewed, fixed, and verified locally against current Why it was redeslint 10's recommended set turns on two rules this codebase breaks in nine places. Both findings are real, so they are fixed rather than disabled.
and nothing survives to say the real failure was
Worth noting
Verificationtypecheck, lint, format, docs clean; 1671 tests pass, 19 skipped. Checked the touched modules directly too — |
|
Verified the combined result after #262 merged: the lockfile merges coherently ( |
This branch was cut before #262 and #263 landed, so merging main produced a pnpm-lock.yaml that git resolved cleanly and pnpm rejected: ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY Broken lockfile: no entry for 'eslint@10.8.0(jiti@1.21.7)' in pnpm-lock.yaml which is why CI failed at "Install dependencies" before running a single check. Regenerated with --no-frozen-lockfile and re-verified with --frozen-lockfile, the flag CI actually uses. eslint 10.9.0 adds no findings on top of the nine that #263 fixed: typecheck, lint, format, docs clean; 1672 tests pass, 19 skipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
#276) * chore(deps-dev): Bump eslint from 10.8.0 to 10.9.0 in the eslint group Bumps the eslint group with 1 update: [eslint](https://github.com/eslint/eslint). Updates `eslint` from 10.8.0 to 10.9.0 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v10.8.0...v10.9.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.9.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: eslint ... Signed-off-by: dependabot[bot] <support@github.com> * chore: repair the lockfile after merging main This branch was cut before #262 and #263 landed, so merging main produced a pnpm-lock.yaml that git resolved cleanly and pnpm rejected: ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY Broken lockfile: no entry for 'eslint@10.8.0(jiti@1.21.7)' in pnpm-lock.yaml which is why CI failed at "Install dependencies" before running a single check. Regenerated with --no-frozen-lockfile and re-verified with --frozen-lockfile, the flag CI actually uses. eslint 10.9.0 adds no findings on top of the nine that #263 fixed: typecheck, lint, format, docs clean; 1672 tests pass, 19 skipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: oratis <wangharp@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
1 participant
Bumps @eslint/js from 9.39.4 to 10.0.1.
Release notes
Sourced from @eslint/js's releases.
... (truncated)
Commits
84fb885chore: package.json update for@eslint/jsrelease1f66734chore: addeslinttopeerDependenciesof@eslint/js(#20467)f3fbc2fchore: set@eslint/jsversion to 10.0.0 to skip releasing it (#20466)b4b3127chore: package.json update for@eslint/jsrelease0b14059chore: package.json update for@eslint/jsreleasefa31a60feat!: addnameto configs (#20015)1e2cad5chore: package.json update for@eslint/jsrelease454a292feat!: updateeslint:recommendedconfiguration (#20210)c6358c3feat!: Require Node.js^20.19.0 || ^22.13.0 || >=24(#20160)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)