Skip to content

Conversation

@hlshen
Copy link
Contributor

@hlshen hlshen commented Jan 30, 2026

2.1.1

@hlshen hlshen requested review from itsrakhil and tammam-g January 30, 2026 14:42
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @hlshen, 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 delivers a minor version update for the Firebase VSCode extension, enhancing its stability and user experience. It primarily focuses on updating a core dependency to leverage the latest firebase-tools features and includes a crucial fix to ensure compiler errors and warnings are displayed with appropriate diagnostic levels within the editor.

Highlights

  • Version Update: The Firebase VSCode extension has been updated to version 2.1.1.
  • Dependency Update: The internal firebase-tools dependency has been updated to version 15.5.1.
  • Error Reporting Improvement: Compiler errors and warnings are now surfaced at the correct diagnosis level, addressing issue [VS Code] Surface GQL error at the right diagnosis level #9805.

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

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
Contributor

@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 bumps the version to 2.1.1 and updates the changelog. The changes are consistent across package.json, package-lock.json, and CHANGELOG.md. I have one minor suggestion to improve the changelog's structure.

@@ -1,5 +1,8 @@
## NEXT

## 2.1.1
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

With this release, the ## NEXT section has become empty. It's a good practice to remove this section to keep the changelog clean. It can be re-added when work for the next version begins.

@hlshen hlshen enabled auto-merge (squash) January 30, 2026 16:44
@hlshen hlshen merged commit 69cdbba into main Jan 30, 2026
59 of 60 checks passed
@hlshen hlshen deleted the hlshen/2.1.1 branch January 30, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants