Skip to content

Conversation

Schtroumphy
Copy link

  • [ X ] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Update analyzer dependency to support newer versions

Description

This PR updates the analyzer dependency constraint from ^6.3.0 to >=6.3.0 <9.0.0 to enable compatibility with newer versions of the analyzer package.

Motivation

Currently, intl_translation with its constraint analyzer: ^6.3.0 cannot be used alongside packages that require newer analyzer versions (7.x, 8.x). This creates dependency conflicts in projects using both:

  • Packages requiring intl_translation (like lokalise_flutter_sdk: ^2.1.0)
  • Packages requiring newer analyzer versions (like riverpod_generator: ^3.0.0 which needs analyzer: >=7.0.0 <9.0.0)

Changes

  • Updated the analyzer dependency in pubspec.yaml to be compatible with versions 6.3.0 through 8.x
  • No code changes were needed as the package seems to work with newer analyzer versions

Testing

I've verified that the package continues to function correctly with analyzer 7.x by:

  • Running the package tests
  • Testing in a real Flutter project that uses both intl_translation and packages requiring analyzer 7.x

Impact

This change allows developers to use intl_translation alongside other packages that require newer analyzer versions, reducing dependency conflicts in the Dart/Flutter ecosystem.

@Schtroumphy Schtroumphy requested a review from mosuem as a code owner September 17, 2025 09:32
Copy link

google-cla bot commented Sep 17, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Schtroumphy, I'm Gemini Code Assist1! 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 addresses a common dependency conflict by broadening the compatible versions of the analyzer package for intl_translation. By updating the pubspec.yaml to support analyzer versions up to 8.x, it ensures that intl_translation can coexist with other packages that have stricter or newer analyzer requirements, thereby enhancing the overall compatibility within Dart/Flutter projects.

Highlights

  • Dependency Update: The analyzer dependency constraint has been updated from ^6.3.0 to >=6.3.0 <9.0.0 in pubspec.yaml.
  • Compatibility: This change enables intl_translation to be compatible with newer versions of the analyzer package (7.x and 8.x), resolving potential dependency conflicts.
  • No Code Changes: No functional code changes were required, indicating that intl_translation works as expected with the broader range of analyzer versions.
  • Impact: The update allows developers to use intl_translation alongside other packages that require more recent analyzer versions, improving ecosystem flexibility.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates the analyzer dependency constraint in pubspec.yaml to '>=6.3.0 <9.0.0', resolving potential dependency conflicts for users of intl_translation. The change is well-motivated and will improve the package's compatibility within the ecosystem. This is a valuable improvement. To make the PR complete, please consider adding an entry to CHANGELOG.md to document this important dependency update for users, which is a common practice for this project.

@Schtroumphy Schtroumphy reopened this Sep 17, 2025
@Schtroumphy Schtroumphy force-pushed the update-analyzer-compatibility branch from b1b093f to 835d6cf Compare September 17, 2025 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant