chore: prepare rules for release

[ematipico]

Summary

Test Plan

Docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 91342b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change updates version metadata for two lint rules. In crates/biome_js_analyze/src/lint/nursery/no_jsx_literals.rs, the NoJsxLiterals rule’s version is set from "next" to "2.2.4". In crates/biome_json_analyze/src/lint/nursery/no_duplicate_dependencies.rs, the NoDuplicateDependencies rule’s version is set from "next" to "2.2.4". No behavioural logic or diagnostics are altered; only the declared version fields in the lint rule metadata are modified.

Possibly related PRs

• ci: improve rule version metadata automation #7429: Adjusts rule version metadata and adds CI automation for updating versions to "2.2.4".
• chore: fix rule version metadata, add script to automate it #7412: Updates lint rule versions from "next" to release strings and introduces a script to automate these updates.
• chore(lint): remove extra v from rule metadata #7150: Fixes and normalises the version field values in declare_lint_rule! metadata across rules.

Suggested labels

A-Linter, L-JavaScript, L-JSON

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 755ea73 and 91342b4.

📒 Files selected for processing (2)

• crates/biome_js_analyze/src/lint/nursery/no_jsx_literals.rs (1 hunks)
• crates/biome_json_analyze/src/lint/nursery/no_duplicate_dependencies.rs (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/version-rules

---

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

[codspeed-hq]

CodSpeed Performance Report

Merging #7449 will not alter performance

_{Comparing chore/version-rules (91342b4) with main (755ea73)}

Summary

✅ 133 untouched benchmarks