Bump @typescript-eslint/eslint-plugin from 8.66.0 to 8.67.0

[dependabot]

Bumps @typescript-eslint/eslint-plugin from 8.66.0 to 8.67.0.

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.67.0

8.67.0 (2026-08-10)

🚀 Features

• typescript-eslint: export basic globs for using tseslint (#12105)

❤️ Thank You

• Evyatar Daud @​StyleShit
• Josh Goldberg ✨
• Kirk Waiblinger @​kirkwaiblinger

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.67.0 (2026-08-10)

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Commits

• 20a261f chore(release): publish 8.67.0
• 6dfe4d0 chore(eslint-plugin-internal): [plugin-test-formatting] enforce zero-indentat...
• 3b155bb chore: use typescript 7 for typechecking (#12601)
• See full diff in compare view

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Akanksha Jain (jainakanksha-msft)]

Dependabot (@dependabot) rebase

[Copilot]

Copilot wasn't able to review any files in this pull request.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version) from the PR diff/description, search the codebase for where that dependency is actually used, and summarize what could be affected.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line summary of any code changes made).
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — post a final comment explaining why this update matters, what the impact/risk is, and what could go wrong if it weren't applied, along with your self-rating and reasoning.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version) from the PR diff/description, search the codebase for where that dependency is actually used, and summarize what could be affected.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line summary of any code changes made).
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — post a final comment explaining why this update matters, what the impact/risk is, and what could go wrong if it weren't applied, along with your self-rating and reasoning.

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — identify what changed (package name, old → new version...

Done. This bumps the lockfile-resolved @typescript-eslint/eslint-plugin/@typescript-eslint/parser from 8.66.0 to 8.67.0 (declared package.json ranges stay ^8.65.0, since these are dev-only lint tooling with no runtime usage in src/).

• npm ci --legacy-peer-deps and npm run build succeed.
• npm run lint passes cleanly with no new rule violations, so no code or eslint.config.js changes were needed.
• No tests/** changes needed since this is a lint-tooling-only bump with no behavioral impact on the storage emulator.
• Added a ChangeLog.md entry under ## Upcoming Release → General: (commit 2b1c1a0... see latest push).

Self-rating: 9/10 — correctness, build/lint health, and changelog accuracy are solid; docked one point since there's no dedicated test to add for a lint-tooling patch bump (none is meaningfully possible here). Risk of not applying this update is low (minor lint rule/perf fixes upstream), but keeping dev tooling current avoids future compounding upgrade pain.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

ChangeLog.md:40

• Sentence after the period should be capitalized for correct grammar ("Updated", not "updated").

- Bumped `cross-env` dev dependency from `^7.0.3` to `^10.1.0`. Cross-env 10 is ESM-only and moved its bin scripts from `src/bin/` to `dist/bin/`. updated `tests/packageScripts.test.ts` to resolve the `cross-env-shell` script from cross-env's declared `bin` mapping.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (3)

ChangeLog.md:40

• Sentence after the second period starts with lowercase updated, which reads like a typo in the changelog. Capitalize it (and consider keeping the same sentence structure/tone as nearby entries).

- Bumped `cross-env` dev dependency from `^7.0.3` to `^10.1.0`. Cross-env 10 is ESM-only and moved its bin scripts from `src/bin/` to `dist/bin/`. updated `tests/packageScripts.test.ts` to resolve the `cross-env-shell` script from cross-env's declared `bin` mapping.

ChangeLog.md:44

• This bullet mixes verb tenses: bumped ... and dedupe .... For readability/grammar, use consistent past tense (e.g., ... and deduped ...) and consider adding a comma before the final clause if keeping it as a single long sentence.

- Relaxed the `serialize-javascript` override from the exact `7.0.3` pin to `^7.0.7` (resolves to 7.1.0) to remediate GHSA-qj8w-gfj5-8c6v (CPU-exhaustion DoS, affects 5.0.0 - 7.0.4), and bumped `mocha` dev dependency from `12.0.0-rc.5` to `12.0.0-rc.6` and dedupe the transitive `serialize-javascript`/`iconv-lite` copies.

.github/copilot-dependabot-instructions.md:7

• The phrase concise/crisp is a bit ambiguous for contributors (and mixes two similar adjectives). Consider simplifying to a single unambiguous instruction (e.g., just concise) to reduce interpretation differences.

5. **Changelog** — append one bullet to `ChangeLog.md` under `## Upcoming Release` → `General:`, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line concise/crisp summary of any code changes made).

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

ChangeLog.md:46

• Minor: this entry reads like a package.json version bump, but package.json still declares ^8.65.0 for both packages (the change is a lockfile-resolved update). To match the wording used for @types/node above, consider rephrasing this as a lockfile-resolved update for accuracy.

- Bumped the `@typescript-eslint/eslint-plugin` and `@typescript-eslint/parser` dev dependencies from 8.66.0 to 8.67.0 (declared `package.json` ranges remain `^8.65.0`).