Update package20260617

[isamu]

Summary by CodeRabbit

• Chores
  • Updated development tooling dependencies to latest stable versions for improved code quality and typing support.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0c4f54b0-7dd5-49fa-8240-6a3aa4f45f6b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Root package.json devDependencies updated: @types/node bumped to ^25.9.3, eslint to ^10.5.0, prettier to ^3.8.4, and typescript-eslint to ^8.61.1. No other changes.

Changes

Dev Dependency Version Bumps

Layer / File(s)	Summary
Root devDependency version bumps package.json	@types/node bumped to ^25.9.3, eslint to ^10.5.0, prettier to ^3.8.4, and typescript-eslint to ^8.61.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• receptron/graphai#1321: Directly overlaps with this PR — same root package.json devDependency bumps for @types/node, eslint, prettier, and typescript-eslint.

Poem

🐇 Hop, hop, a version bump today,
eslint and prettier on their way!
typescript-eslint leaps ahead with glee,
@types/node joins the jubilee.
Small patches, tidy deps — hooray! 🌿

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update package20260617' is vague and non-descriptive, using a timestamp pattern that conveys no meaningful information about the actual dependency updates being made.	Revise the title to clearly describe the changes, e.g., 'Update dev dependencies: @types/node, eslint, prettier, and typescript-eslint' or similar descriptive language.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch updatePackage20260617

---

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.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typescript-eslint@​8.59.4 ⏵ 8.61.1
	@​types/​node@​25.9.0 ⏵ 25.9.3	+1		+1
	@​google/​genai@​2.4.0 ⏵ 2.8.0	+1			+2
	prettier@​3.8.3 ⏵ 3.8.4	+1		+1
	eslint@​10.4.0 ⏵ 10.5.0	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/typescript-eslint@8.61.1 → npm/@typescript-eslint/eslint-plugin@8.61.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.61.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report