chore(deps): april updates

[basmasking]

Fixes #632

Changes proposed in this pull request:

• april updates

@MaskingTechnology/jitar

Summary by CodeRabbit

• Chores
  • Updated several development dependencies to their latest versions.
  • Upgraded the "dotenv" dependency to a newer version in relevant packages.
  • Removed an unused development dependency.

[coderabbitai]

Walkthrough

This update modifies the dependency versions in three package.json files. The root package.json receives updates to several development dependencies, with one type definition removed. The dotenv dependency is updated to a newer version in both the @jitar/configuration and @jitar/jitar packages. No changes are made to any source code, exported entities, or scripts.

Changes

File(s)	Change Summary
package.json	Updated multiple devDependencies to newer versions and removed @types/eslint__js from devDependencies.
packages/configuration/package.json packages/jitar/package.json	Updated the dotenv dependency from ^16.4.7 to ^16.5.0.

Assessment against linked issues

Objective	Addressed	Explanation
Update dependencies as specified for April (#632)	✅

Poem

A hop, a skip, dependencies rise,
With April's breeze, new versions surprise.
Dotenv refreshed, the code’s still neat,
Old types removed, our build is fleet.
With every update, we leap ahead—
A rabbit’s cheer for code well-fed! 🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0fef759 and 86b0b73.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• package.json (1 hunks)
• packages/configuration/package.json (1 hunks)
• packages/jitar/package.json (1 hunks)

🔇 Additional comments (6)

packages/jitar/package.json (1)

29-29: Confirm the dotenv version bump is compatible
You’ve updated dotenv from ^16.4.7 to ^16.5.0. Please review the release notes for any breaking changes (e.g., encoding or parsing behavior adjustments) and ensure the runtime behavior remains unchanged in both local and CI environments.

packages/configuration/package.json (1)

21-21: Align dotenv across packages
Version ^16.5.0 now matches the bump in packages/jitar. This keeps environment‐loading consistent across your monorepo. No other dependency changes here—looks good to merge.

package.json (4)

25-27: Approve core tooling version updates
Bumping @changesets/cli to ^2.29.2, @eslint/js to ^9.25.0, and @nx/eslint-plugin to ^20.8.0 ensures up‐to‐date changelog and linting workflows. Verify that existing CLI scripts and lint configurations remain compatible.

---

36-37: Validate testing and coverage tooling updates
Upgrading @typescript-eslint/eslint-plugin to ^8.30.1 and @vitest/coverage-v8 to ^3.1.1 can affect lint rules and coverage outputs. Run npm run test and npm run test-coverage to catch any deprecations or report regressions.

---

39-39: Verify eslint major version bump
Moving to eslint@^9.25.0 may introduce new rules or changes in core behavior. Confirm that your existing .eslintrc settings still apply and consider pinning shared configs across workspaces.

---

42-44: Confirm build pipeline compatibility
Updating rollup to ^4.40.0, rollup-plugin-dts to ^6.2.1, and turbo to ^2.5.0 might require tweaks in your Rollup/Turbo configs. Please execute npm run build and npm run build:all to ensure successful bundling and type generation.

[coderabbitai]

⚠️ Potential issue

Check for a potential typo in ESLint plugin
The dependency "typescript-eslint": "^8.30.1" (without the @ scope) looks unusual compared to the scoped packages. Double‑check if this is intentional or if it should reference @typescript-eslint/typescript-estree or another scoped package.