refactor: Bump eslint from 10.1.0 to 10.2.0

[mtrezza]

Closes #217

Changes

• Bumps eslint from 10.1.0 to 10.2.0 (minor, devDependency)
• See release notes: eslint/eslint v10.2.0

Breaking Changes

None.

Code Changes Required

None.

Summary by CodeRabbit

• Chores
  • Bumped development tool eslint from 10.1.0 to 10.2.0.
  • Updated the lockfile to refresh eslint’s bundled packages and metadata for consistent installs and improved stability.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 05a1cd0b-16ef-45dc-8201-6251552c96fc

📥 Commits

Reviewing files that changed from the base of the PR and between 0af389d and 78d8c2c.

📒 Files selected for processing (2)

• package-lock.json
• package.json

✅ Files skipped from review due to trivial changes (1)

• package.json

🚧 Files skipped from review as they are similar to previous changes (1)

• package-lock.json

---

📝 Walkthrough

Walkthrough

Bumped ESLint dev dependency from 10.1.0 to 10.2.0 in package.json and updated package-lock.json entries accordingly, including updated pinned versions and integrity metadata for ESLint and several first-party transitive packages.

Changes

Cohort / File(s)	Summary
ESLint Dependency Update package.json	Updated devDependency eslint version specifier from 10.1.0 → 10.2.0.
Lockfile Synchronization package-lock.json	Updated lockfile entries: eslint tarball resolved URL/integrity and pinned ranges/versions for first-party packages (@eslint/config-array, @eslint/config-helpers, @eslint/core, @eslint/object-schema, @eslint/plugin-kit) adjusted to align with ESLint v10.2.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• refactor: Bump eslint from 7.32.0 to 9.39.3 #198 — Also updates the project's ESLint dev dependency and corresponding lockfile entries.

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	Review feedback comments and discussions on GitHub PR #220 are not accessible through local repository filesystem.	Access GitHub PR #220 via API or web interface to verify user engagement with review comments and feedback threads.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'refactor: Bump eslint from 10.1.0 to 10.2.0' begins with the required 'refactor:' prefix and accurately describes the dependency version bump in the changeset.
Description check	✅ Passed	The PR description deviates from the required template by using 'Changes' instead of the templated 'Approach' section, and omits the 'Tasks' section, but provides the essential information with issue closure link.
Linked Issues check	✅ Passed	The PR successfully updates eslint from 10.1.0 to 10.2.0 as required by issue #217, with corresponding package.json and package-lock.json changes reflecting the new dependency versions.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly related to the eslint dependency update specified in issue #217; no unrelated modifications to other dependencies or code are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	ESLint updated from 10.1.0 to 10.2.0 with security-focused bug fixes, no breaking changes, and only dev dependency impacts.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.2.513)

package.json

2026-04-10 20:32:02,332 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 20:32:02,333 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 20:32:02,334 [MainThread ] [ERROR] Template file not found: package.json
2026-04-10 20:32:02,398 [MainThread ] [ERROR] Failed to invoke function /usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner. with package.json
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 88, in func_wrapper
result = original_func(item)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 74, in
results = parallel_runner.run_function(lambda f: (f, self._parse_file(f)), files_to_load)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/ope

... [truncated 2547 characters] ...

[MainThread ] [WARNI] Secret scanning: could not process file package.json
2026-04-10 20:32:02,458 [MainThread ] [ERROR] Exception traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/main.py", line 647, in run
self.scan_reports = runner_registry.run(
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/runner_registry.py", line 177, in run
for result in parallel_runner_results:
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 118, in _run_function_multiprocess_fork
raise v.internal_exception.with_traceback(v.internal_exception.traceback)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (6909a2e) to head (78d8c2c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #220   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          159       159           
=========================================
  Hits           159       159           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.