chore(deps): update dependency eslint to v10.8.1

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint (source)	10.8.0 → 10.8.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

eslint/eslint (eslint)

v10.8.1

Compare Source

Bug Fixes

• 18eb0a7 fix: prevent ASI hazard in no-unused-labels autofix (#​21173) (dongkyu lee)
• 151ba3f fix: false positives in getter-return and accessor-pairs (#​21163) (Grit)
• 6898df9 fix: ignore meta-property names in id-denylist (#​21166) (Pixel)
• 4d7db66 fix: ignore meta-property names in id-match (#​21167) (Pixel)
• 677214e fix: handle ASI hazards in no-unused-vars removeVar suggestion (#​20935) (kuldeep kumar)

Documentation

• 7d0cbf8 docs: Update README (GitHub Actions Bot)
• 0a05812 docs: add missing backticks to no-duplicate-imports.js (#​21183) (Lee Daeun)
• 678c90b docs: Update README (GitHub Actions Bot)
• 8a10424 docs: Update README (GitHub Actions Bot)
• 69bb948 docs: Update README (GitHub Actions Bot)

Chores

• 0a14800 chore: update github/codeql-action action to v4.37.4 (#​21196) (renovate[bot])
• 05adcb1 test: fix failing ecosystem test for eslint-plugin-unicorn (#​21191) (Lazizbek Ergashev)
• 5611035 test: add error locations info to no-void (#​21185) (Lee Daeun)
• ee47333 ci: bump github/codeql-action from 4 to 4.37.3 (#​21176) (dependabot[bot])
• f131c03 chore: improve ecosystem test failure reporting (#​20937) (crimsonjay0)
• 1f6edde chore: update ecosystem plugins (#​21182) (ESLint Bot)
• d3266fb chore: unpin webpack dependency (#​21172) (Francesco Trotta)
• 65a6519 chore: add allowScripts field to package.json (#​21092) (GiHoon Noh)
• 22e5256 ci: add triage:no label to Dependabot PRs (#​21141) (lumir)
• 55c9038 ci: bump actions/labeler from 6 to 7 (#​21159) (dependabot[bot])
• 7280e78 chore: update dependency prettier to v3.9.6 (#​21162) (renovate[bot])
• eddbad6 test: fix failing ecosystem test for eslint-plugin-unicorn (#​21156) (Francesco Trotta)
• 60a178d chore: update ecosystem plugins (#​21150) (ESLint Bot)
• f9f61dc test: add error locations to no-unreachable (#​21151) (JIYEON)
• d086293 test: add error locations to no-undef (#​21147) (JIYEON)
• cc01b67 test: add error locations to no-useless-catch (#​21144) (devoil)
• 688e75e chore: add missing backticks in JSDoc (#​21143) (Bo Hyun Kim)
• 7c1e175 test: add error locations to require-await (#​21145) (Grit)
• 588a26d test: add error locations to no-extra-label (#​21139) (dongkyu lee)
• 059aa89 test: add error locations to no-useless-concat (#​21140) (dongkyu lee)
• 5a452a8 test: add error locations to no-const-assign (#​21138) (dongkyu lee)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:44 AM UTC · Completed 3:50 AM UTC

Commit: d34de62 · View workflow run →

[github-actions]

Site preview

Preview: https://f55c13ab-site.fullsend-ai.workers.dev

Commit: ee4d5f860c8905f3412759425f2f4ce2a9a2518c

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Looks good to me

Previous run

Looks good to me

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:23 PM UTC · Completed 3:30 PM UTC

Commit: ee4d5f8 · View workflow run →

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 3:51 AM UTC · Completed 4:03 AM UTC

Commit: ee4d5f8 · View workflow run →

[fullsend-ai-retro]

Retro: PR #6015 — chore(deps): update dependency eslint to v10.8.1

This was a fully automated Renovate bot PR bumping eslint from 10.8.0 to 10.8.1, changing only package-lock.json (4 additions, 4 deletions). Zero human involvement throughout — no human comments or reviews.

Timeline

1. 2026-08-08 03:43 UTC — Renovate bot opens PR with a single lockfile change.
2. 2026-08-08 03:44–03:50 UTC — First review run dispatches correctness + style-conventions sub-agents with trivial scope constraints. Both return zero findings. Agent correctly identifies the mermaid dev: true reclassification as a lockfile regeneration artifact. Approves.
3. 2026-08-08 15:22 UTC — Renovate rebases the PR (no effective diff change).
4. 2026-08-08 15:22–15:30 UTC — Second review run triggered by the rebase. Follows re-review protocol — identifies the Containerfile delta as base-branch advancement, verifies mermaid is only used in VitePress docs. Approves again. Cost: $1.81.
5. 2026-08-09 03:48 UTC — PR auto-merged.
6. 2026-08-09 03:49 UTC — Retro run dispatched.

What went well

• Review quality was appropriate. The agent correctly scoped the review as trivial, dispatched only 2 of 6 available sub-agents, applied reduced tool-call budgets, and identified the lockfile regeneration side-effect (mermaid reclassification) without raising a false positive.
• Re-review protocol worked correctly. The second run followed the delta-based re-review path rather than blindly re-running the full review, correctly filtering base-branch noise from the Containerfile change.
• No false positives. Zero unnecessary findings on a PR that warranted zero findings.

Inefficiency: dispatch-layer waste on trivial bot PRs

The primary inefficiency is at the dispatch layer, not the agent layer. This PR consumed ~2 review runs (est. $3–4 total) plus a retro run on a lockfile-only patch bump from a trusted bot that auto-merges. The review agent did its job well once dispatched — the question is whether it should have been dispatched at all, or dispatched a second time after a no-op rebase.

No new proposals — existing issues cover this comprehensively

All improvement areas identified are already covered by extensive open issues:

• Skip/reduce review for bot dependency PRs: Skip review and retro stages for bot-authored dependency update PRs #5360, Skip fullsend agent dispatch for bot dependency PRs #5067, Skip agent stages for auto-merge bot PRs to reduce wasted compute #4975, Consider skipping or minimizing review agent runs on bot-authored dependency update PRs #4796, Consider skipping or reducing agent effort on automated dependency update PRs #4177, pr-review skill: reduce sub-agent dispatch for mechanical/value-only changes like dependency bumps #4060, Review agent: fast-path bot-authored dependency digest PRs #4293, Consider fast-path for review agent on single-file bot dependency PRs #3347, Add review fast-path triage to skip unnecessary sub-agents for trivially safe bot PRs #3240, Review agent: use cheaper model for trivial bot-authored PRs #2842, Add fast-path in review orchestrator for trivial bot-authored PRs #2639, Add lightweight review path for trivial bot dependency bumps #1358 all propose variants of fast-pathing or skipping review for trivial bot PRs.
• Skip redundant rebase re-reviews: Review agent should avoid full re-reviews when Renovate rebases without content changes #4596, Skip redundant re-reviews when Renovate rebases a dependency PR without changing the diff #4652, Review agent should detect rebase-only force-pushes and skip re-review when the effective diff is unchanged #4401, Skip re-review when bot dep-bump PR is rebased with no semantic change #1355, Skip or diff-gate re-review when PR changes are rebase-only #1287, Skip re-review when PR diff is unchanged after rebase/reopen #1356, Pre-review script should skip dispatch when merge commit SHA matches the last completed review #3673 all propose detecting rebase-only pushes and skipping re-review.
• Skip retro for bot PRs: Skip retro agent for automated bot dependency PRs #3833, Skip retro stage for automated dependency PRs (Renovate, Dependabot, MintMaker) #4006, Skip retro agent for bot-authored trivial PRs with no agent interaction #3226, Skip or use lightweight retro analysis for bot-authored PRs #3317, Skip retro dispatch for any unmerged PR with zero fullsend agent involvement #5943, Skip retro dispatch for merged PRs with zero meaningful agent involvement #5399 all propose skipping retro dispatch for bot-authored dependency PRs.
• Consolidation meta-issue: Consolidate 22+ overlapping "skip retro/agent dispatch" issues into a single design issue #5817 explicitly calls out 22+ overlapping issues in this space and proposes consolidating them into a single design issue.

This retro provides additional evidence for those existing issues: PR #6015 consumed an estimated $3–4 in review costs plus retro costs for a 4-line lockfile patch bump that passed CI and auto-merged with zero human interaction. The retro itself is a case in point — analyzing a workflow that went correctly and predictably, producing no novel findings.