chore(renovate): include @babel scope in build tooling group

[Mehdi-Bl]

Summary

• add ^@babel/ to Renovate build-tooling package grouping

Context

This addresses the valid unresolved review thread on PR #20 about Babel-scoped packages not being grouped with other build tooling updates.

Notes

• I did not enable setup-node package cache because this repo currently enforces package-manager-cache: false to satisfy workflow hardening/zizmor cache-poisoning policy.

Summary by Sourcery

Build:

• Update Renovate configuration to group @babel-scoped packages with other build tooling dependencies.

Summary by CodeRabbit

• Chores
  • Updated build tooling dependency management configuration to improve package organization and automation.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Renovate configuration so that all @babel-scoped packages are included in the existing build tooling dependency update group, aligning dependency management behavior with prior review feedback.

File-Level Changes

Change	Details	Files
Include @babel-scoped packages in the Renovate build-tooling group.	Extend the build-tooling packageRules to match packages with the @babel/ scope (e.g., via a '^@babel/' pattern). Ensure that Babel-related dependencies are grouped with other build tooling updates in Renovate PRs, as requested in a previous review thread.	renovate.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Include @babel scoped packages in build tooling group

✨ Enhancement

Walkthroughs

Description

• Add ^@babel/ pattern to build tooling group
• Ensures scoped Babel packages grouped with other build tools
• Resolves unaddressed review feedback from previous PR

Diagram

flowchart LR
  A["renovate.json<br/>build tooling rule"] -- "add @babel/ pattern" --> B["Scoped Babel packages<br/>grouped with build tools"]

Loading

File Changes

1. renovate.json ⚙️ Configuration changes +1/-1

Add @babel scope to build tooling group

• Added ^@babel/ pattern to build tooling package grouping
• Ensures scoped Babel packages are grouped with webpack, eslint, and prettier
• Addresses review feedback about missing Babel scope in grouping configuration

renovate.json

---

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[gemini-code-assist]

Summary of Changes

Hello @Mehdi-Bl, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the dependency management configuration by updating Renovate's grouping rules. The change ensures that all Babel-related packages, including those under the @babel scope, are correctly categorized and updated alongside other essential build tooling, streamlining the dependency update process and addressing previous grouping inconsistencies.

Highlights

• Renovate Configuration Update: Modified renovate.json to include @babel scoped packages within the "build tooling" group, ensuring these dependencies are grouped for updates.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• renovate.json
  • Added ^@babel/ to the matchPackagePatterns array for the "build tooling" group.

Activity

• The change addresses an unresolved review thread from PR Integrate review feedback for Renovate + CI lockfile installs #20 regarding Babel-scoped packages not being grouped correctly.
• The author explicitly noted that setup-node package cache was not enabled due to the repository's package-manager-cache: false policy, which is in place for workflow hardening/zizmor cache-poisoning.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

📝 Walkthrough

Walkthrough

Renovate configuration updated to include scoped packages under @babel/ in the build tooling package rule's matchPackagePatterns. This expands the scope of packages grouped under "build tooling" to recognize Babel scoped packages alongside existing patterns.

Changes

Cohort / File(s)	Summary
Renovate Configuration renovate.json	Expanded matchPackagePatterns in build tooling package rule to include @babel/ scoped packages alongside existing patterns (webpack, babel, eslint, prettier).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A scoped package hops into view,
@babel/ joins the tooling crew,
Renovate groups them nice and neat,
Build tools bundled, oh so sweet!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding @babel scope to Renovate's build tooling group configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/renovate-babel-group

---

No actionable comments were generated in the recent review. 🎉

---

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

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

ⓘ The new review experience is currently in Beta. Learn more

[gemini-code-assist]

Code Review

This pull request correctly updates the Renovate configuration to group @babel scoped packages under the 'build tooling' category. The addition of the ^@babel/ pattern is the right solution for this, and the change is effective. While the change itself is perfect, I noticed a related potential improvement in the same file: the babel-jest pattern in the 'test tooling' group is not anchored (e.g., with ^ and $). This could lead to unintended matches with other packages. You might consider changing it to ^babel-jest$ in a future change to make the pattern more precise.