chore(deps-dev): Bump the typescript group across 1 directory with 2 updates - #262
Conversation
…updates Bumps the typescript group with 2 updates in the / directory: [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) and [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/vscode). Updates `typescript-eslint` from 8.65.0 to 8.67.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.67.0/packages/typescript-eslint) Updates `@types/vscode` from 1.120.0 to 1.125.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/vscode) --- updated-dependencies: - dependency-name: "@types/vscode" dependency-version: 1.125.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: typescript - dependency-name: typescript-eslint dependency-version: 8.66.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: typescript ... Signed-off-by: dependabot[bot] <support@github.com>
468de28 to
7885633
Compare
…rn/typescript-71c6988b94
The typescript group swept `@types/vscode` from ^1.85.0 to ^1.125.0 along with typescript-eslint, and `vsce package` refused the build: ERROR @types/vscode ^1.125.0 greater than engines.vscode ^1.85.0 That check is right. `engines.vscode` is the OLDEST editor this extension supports; types newer than it let a call added in a later VS Code typecheck cleanly and then fail on the editor we promised to run on. Taking the bump means dropping every VS Code between 1.85 and 1.125, which is a support decision, not a dependency update. typescript-eslint ^8.67.0 is kept — it was the half of the group that had nothing wrong with it. Pinned exactly rather than restored to `^1.85.0`: the caret was already resolving to 1.120.0 on main, so the compiler was seeing 35 minor versions of API the extension does not claim to support. Verified the floor is honest — `apps/vscode` typechecks against exactly 1.85.0 with no errors — so the pin costs nothing and makes the declaration enforceable. Guarded twice: dependabot is told to ignore the dependency, with the reason written down, and `scripts/vscode-types-engine.test.ts` fails the unit suite in seconds rather than waiting for `release:check` to fail minutes into a full workspace build. release:check exits 0; VSIX packages at 199.19 KB. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Reviewed, fixed, and verified locally against current Why it was redThe group swept That check is correct and should not be worked around. So: One thing found while fixing itRestoring Pinned exactly ( Guarded twice
Verificationtypecheck, lint, format, docs clean; 1672 tests pass, 19 skipped; |
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>
Bumps the typescript group with 2 updates in the / directory: typescript-eslint and @types/vscode.
Updates
typescript-eslintfrom 8.65.0 to 8.67.0Release notes
Sourced from typescript-eslint's releases.
Changelog
Sourced from typescript-eslint's changelog.
Commits
20a261fchore(release): publish 8.67.0c245fbbfeat(typescript-eslint): export basic globs for using tseslint (#12105)3b155bbchore: use typescript 7 for typechecking (#12601)e51b11bchore(release): publish 8.66.0Updates
@types/vscodefrom 1.120.0 to 1.125.0Commits