Update dependency eslint-plugin-sonarjs to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-sonarjs (source)	3.0.7 → 4.0.0

---

Release Notes

SonarSource/SonarJS (eslint-plugin-sonarjs)

v4.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

Updated both pr-review and pr-summary packages to use eslint-plugin-sonarjs version 4.0.0, ensuring lint rules stay current with upstream improvements.

Walkthrough

• Chore: Bumped eslint-plugin-sonarjs from 3.0.7 to 4.0.0 in both package.json files to keep development dependencies up to date and maintain consistency across projects.

_{Model: o4-mini-2025-04-16 | Prompt Tokens: 438 | Completion Tokens: 493}

[github-actions]

Here is a gentle code review powered by AI that aims to support your progress. Some feedback may be predictions rather than definitive answers, so feel free to adopt what resonates with you. You drive the process—AI is here simply to help.
_{Model: o4-mini-2025-04-16 | Prompt Tokens: 880 | Completion Tokens: 2895}

[github-actions]

You've updated eslint-plugin-sonarjs from 3.0.7 to 4.0.0, a major release with possible breaking changes. Please:

• Review the plugin's changelog or migration guide for any breaking changes.
• Adjust your ESLint configuration if new rules are introduced or defaults have changed.
• Consider using a caret range (^4.0.0) instead of pinning to an exact version to allow for non-breaking patch updates.

Example:

{
  ...
  "eslint-plugin-sonarjs": "^4.0.0",
  ...
}

After updating the specifier, run npm install (or yarn install) to regenerate your lockfile and ensure dependency consistency across environments.

[github-actions]

You've updated eslint-plugin-sonarjs from 3.0.7 to 4.0.0, a major release with possible breaking changes. Please:

• Review the plugin's changelog or migration guide for any breaking changes.
• Adjust your ESLint configuration if new rules are introduced or defaults have changed.
• Consider using a caret range (^4.0.0) instead of pinning to an exact version to allow for non-breaking patch updates.

Example:

{
  ...
  "eslint-plugin-sonarjs": "^4.0.0",
  ...
}

After updating the specifier, run npm install (or yarn install) to regenerate your lockfile and ensure dependency consistency across environments.

[github-actions]

This update bumps various dependencies in both the PR review and summary packages to their latest releases, ensuring the SAP AI SDK modules, linting tools, and utility libraries stay current.

Walkthrough

• Chore: Upgraded @sap-ai-sdk/ai-api and @sap-ai-sdk/orchestration from 2.6.0 to 2.7.0
• Chore: Patched minimatch from 10.2.0 to 10.2.2
• Chore: Updated ESLint ecosystem—eslint, @eslint/js, eslint-plugin-sonarjs, and typescript-eslint to their newest versions
• Chore: Kept other dev dependencies like TypeScript, Prettier, and YAML support at current stable releases

_{Model: o4-mini-2025-04-16 | Prompt Tokens: 1062 | Completion Tokens: 634 | Diff Range: 55408c4...299f7e1}

[github-actions]

We’re happy to share personalized feedback on your code with the help of AI. These ideas are friendly suggestions rather than absolute truths—feel free to choose what resonates. Your judgment and creativity guide the final outcome, and AI is here simply to support your decisions.
_{Model: o4-mini-2025-04-16 | Prompt Tokens: 880 | Completion Tokens: 1501 | Diff Range: 55408c4...299f7e1}

[github-actions]

You’re bumping eslint-plugin-sonarjs from 3.x to 4.x, which is a major upgrade and may introduce breaking changes in rule names, behavior, or defaults. Make sure to:

• Review the changelog for any renamed or removed rules and update your ESLint config accordingly.
• Run a full lint pass to catch new warnings or errors.
• Update your lockfile (e.g., package-lock.json or pnpm-lock.yaml).

Also, consider using a caret range to allow future non-breaking updates automatically:

"eslint-plugin-sonarjs": "^4.0.0"

[github-actions]

This module has the same devDependencies as pr-review. To avoid duplication and reduce maintenance overhead, consider centralizing shared ESLint tooling in a workspace root or a shared configuration package. For example, in your root package.json:

{
  "devDependencies": {
    "eslint-plugin-sonarjs": "^4.0.0",
    "eslint": "^9.39.3",
    "eslint-plugin-unicorn": "^63.0.0",
    // …
  }
}

Then each sub-package can extend the shared ESLint config, keeping versions in sync across the repo.