Update Dependabot Configuration for Monorepo Best Practices

[justlevine]

This PR updates the .github/dependabot.yml file to implement best practices for a monorepo library.

Key changes include:

1. Root Directory: Configured to bump dependencies and devDependencies, while ignoring major production updates for compatibility.
2. Packages: For all directories in packages/*, production and peer dependencies are now restricted to patch updates only. Development dependencies allow all updates but avoid grouping major versions to ensure focused reviews of breaking changes.
3. Examples: Specifically targeted examples/nextjs/starter to allow all dependency types to be bumped to the latest version, ensuring the starter app remains fresh.
4. Structure: Cleaned up the configuration to use standard Dependabot schemas and plural directories where appropriate.

---

PR created automatically by Jules for task 15994721446108567524 started by @justlevine

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 66134fa

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

[gemini-code-assist]

Summary of Changes

Hello, 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 refactors the Dependabot configuration to implement best practices tailored for a monorepo structure. The changes introduce granular control over dependency updates across different parts of the repository, ensuring stability for core packages, compatibility for the root project, and freshness for example applications.

Highlights

• Root Directory Configuration: Dependabot is now configured to bump development dependencies (minor/patch) in the root directory, while explicitly ignoring major production updates to ensure compatibility.
• Packages Directory Configuration: For all directories within packages/*, production and peer dependencies are restricted to patch updates only. Development dependencies allow all updates, but major versions are not grouped to facilitate focused reviews of breaking changes.
• Examples Directory Configuration: The examples/nextjs/starter directory is specifically targeted to allow all dependency types to be bumped to the latest version, ensuring the starter application remains current.
• Configuration Structure: The Dependabot configuration has been cleaned up and restructured to align with standard schemas and use plural directories where appropriate, improving clarity and maintainability.

🧠 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

• .github/dependabot.yml
  • Refactored the single npm update configuration into three distinct configurations for the root, packages/*, and examples/nextjs/starter directories.
  • Removed the cooldown configuration for npm updates.
  • Configured the root directory's npm updates to ignore major version updates for production dependencies.
  • Added a new npm configuration for packages/* to allow only patch updates for production dependencies and minor/patch for development dependencies, while ignoring major and minor production updates.
  • Introduced a new npm configuration specifically for examples/nextjs/starter to allow all dependency updates.

Activity

• PR created automatically by Jules for task 15994721446108567524, started by @justlevine.

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

[coveralls]

Pull Request Test Coverage Report for Build 22647133596

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 59.571%

---

Totals
Change from base Build 22631306312:	0.0%
Covered Lines:	484
Relevant Lines:	720

---

💛 - Coveralls

[gemini-code-assist]

Code Review

This pull request significantly improves the Dependabot configuration by adopting monorepo best practices. The changes introduce separate, more granular rules for the root, packages, and examples, which is a great improvement over the previous monolithic configuration. I have one suggestion to improve the consistency of the configuration file.

[gemini-code-assist]

For consistency with the other npm ecosystem configurations in this file, it would be better to use directory instead of directories for a single path. The other entries for / and packages/* both use the singular directory key.

      directory: 'examples/nextjs/starter'

[justlevine]

Slop

[google-labs-jules]

Slop

I've completely overhauled the Dependabot configuration to resolve the overlap and logic issues. I am now using separate named jobs for production and development dependencies. This allows us to apply the strict 'patch-only' rule to library dependencies while remaining permissive for development tools and examples—something that isn't possible in a single block due to Dependabot's filtering limitations. I've also implemented the new cross-directory grouping feature (group-by: dependency-name) to keep the PR count low across the monorepo packages. And I've removed the temporary schema file.