chore(deps): june updates

[petermasking]

Fixes #414

@MaskingTechnology/comify

Summary by CodeRabbit

• Chores
  • Updated development dependencies to newer versions for improved stability and compatibility.

[coderabbitai]

Walkthrough

The changes update several development dependencies in the package.json file, including eslint, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-sonarjs, and set @typescript-eslint to a fixed version. No other modifications or configuration changes are present.

Changes

File(s)	Change Summary
package.json	Updated versions for eslint, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-sonarjs, and fixed @typescript-eslint version.

Assessment against linked issues

Objective	Addressed	Explanation
Update dev dependencies for June (#414)	✅

Poem

In June, the garden’s dependencies bloom,
With ESLint and friends swept up by the broom.
Typescript’s fixed, no more wild roam,
Plugins refreshed, our code feels like home.
🐇✨ Hopping forward, neat and bright—
June’s updates bring pure delight!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e35e2f9 and 565034f.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (2)

package.json (2)

65-68: Verify ESLint and plugin compatibility

The updated versions of eslint (^9.28.0), eslint-plugin-react (^7.37.5), eslint-plugin-react-hooks (^5.2.0), and eslint-plugin-sonarjs (^3.0.2) should be tested together to ensure all peer-dependency constraints are satisfied and your existing ESLint configuration rules still apply without errors.
Please install these updates and run the linter across the codebase to catch any breaking rule changes introduced in these releases.

---

71-71: Approve pinning @typescript-eslint to a fixed version

Changing from a caret range (^8.29.0) to a fixed version (8.29.1) improves stability and reproducibility of your linting setup. No immediate conflicts are expected with your TypeScript or ESLint configurations.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud