chore: Add version constraints for bootstrap dependencies

[spydon]

Summary

• Replaces any with explicit version constraints for collection (^1.19.0), meta (^1.16.0), and path (^1.9.0) under melos.command.bootstrap.dependencies in the root pubspec.yaml
• Complements chore: Add version constraints for collection, meta, and path #995 which fixed the same issue in packages/melos/pubspec.yaml but missed the bootstrap config

Test plan

• Run melos bs to verify bootstrap still resolves correctly
• Run melos exec -- dart pub publish --dry-run to confirm the 3 warnings are gone

[docs-page]

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/melos~996

Documentation is deployed and generated using docs.page.

[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 refines the project's dependency management by replacing broad 'any' version specifications with explicit version constraints for key packages (collection, meta, path) in the root pubspec.yaml's Melos bootstrap configuration. This ensures greater stability and predictability in dependency resolution, preventing potential conflicts and aligning the root configuration with previous fixes made in other parts of the project.

Highlights

• Version Constraints: Explicit version constraints were added for collection (^1.19.0), meta (^1.16.0), and path (^1.9.0) within the melos.command.bootstrap.dependencies section of the root pubspec.yaml.
• Bootstrap Configuration: This change complements a previous fix in chore: Add version constraints for collection, meta, and path #995 by addressing the same dependency constraint issue in the root bootstrap configuration, which was previously overlooked.

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

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.

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

[gemini-code-assist]

Code Review

This pull request updates the collection, meta, and path dependencies in pubspec.yaml to their latest stable versions. A review comment highlights an inconsistency with the path dependency, noting that other parts of the file might reference an invalid version (^1.9.1). To ensure consistency and prevent potential build failures, all path dependency constraints should be aligned to ^1.9.0.