Release/1.5.0

[fulleni]

Status

READY

Description

This pull request is a release preparation for version 1.5.0 of the mobile client. It primarily focuses on updating the project's version number and ensuring all dependencies are current. This includes bumping versions for several internal packages and external libraries, alongside a small code style improvement and the removal of a specific dependency override.

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[gemini-code-assist]

Summary of Changes

Hello @fulleni, 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 is a release preparation for version 1.5.0 of the mobile client. It primarily focuses on updating the project's version number and ensuring all dependencies are current. This includes bumping versions for several internal packages and external libraries, alongside a small code style improvement and the removal of a specific dependency override.

Highlights

• Project Version Update: The main project version has been incremented from 1.4.0 to 1.5.0 in pubspec.yaml, aligning with the release preparation.
• Dependency Updates: Numerous dependencies, including both internal git-referenced packages (e.g., auth_api, data_api, ui_kit) and hosted packages (e.g., bloc, go_router, flex_color_scheme), have been updated to their latest versions, as reflected in pubspec.yaml and pubspec.lock.
• Dependency Override Removal: The explicit dependency_overrides entry for the core package has been removed from pubspec.yaml, allowing it to resolve naturally.
• Code Style Refinement: A minor cosmetic change was applied to lib/account/view/account_page.dart to condense the IconButton's icon declaration.

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 prepares for the v1.5.0 release by updating the application version and bumping several dependencies. The changes are mostly related to configuration files (pubspec.yaml, pubspec.lock) and include a minor code formatting improvement. While most dependency updates are standard, I've identified a critical issue with the http-client dependency where a git tag was mutated. This practice undermines build reproducibility and should be addressed to ensure stable builds.