Change version to 500.0, and the untilBuild to 253.*

[jwren]

These changes are anticipation of landing the Dart Plugin in coming days from the Google vendor.

[gemini-code-assist]

Summary of Changes

Hello @jwren, 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 prepares the project for the upcoming integration of the Dart Plugin from the Google vendor. It updates the plugin's internal version number and extends the compatible IntelliJ Platform build range to accommodate these anticipated changes, ensuring future compatibility and alignment with the new plugin release.

Highlights

• Plugin Version Update: The pluginVersion in third_party/gradle.properties has been updated from 89.0 to 500.0.
• Build Compatibility Range Extension: The pluginUntilBuild property in third_party/gradle.properties has been updated from 251.* to 253.*, extending the supported build range.

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

[gemini-code-assist]

Code Review

This pull request updates the plugin version to 500.0 and extends the IDE compatibility range by setting pluginUntilBuild to 253.*. While the changes are straightforward, I've identified a minor inconsistency with the versioning format. The pluginVersion does not fully adhere to the SemVer format mentioned in the file's comments. I've provided a suggestion to align it with the standard, which also supports the project's goals of consistency and maintainability as outlined in the style guide.

[gemini-code-assist]

The comment on line 9 indicates that pluginVersion should follow the SemVer format. To improve consistency and maintainability¹, it's best to adhere to the specified format. The SemVer specification requires a MAJOR.MINOR.PATCH structure. The current value 500.0 is missing the patch version. To adhere to the standard, please update it to 500.0.0.

pluginVersion = 500.0.0

Style Guide References

Footnotes

1. The style guide emphasizes consistency and maintainability. Using the correct SemVer format as declared in the file's comments aligns with these principles. (link) ↩

[jwren]

presubmit caught this minor issue, created #80 to follow up with