Repository navigation
Release/v1.4.5 - #49
Conversation
Release/v1.4.3
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Summary of ChangesHello @Eva813, 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 is a routine version bump, updating the project's release number to Highlights
🧠 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 AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request updates the version number to 1.4.5 in package.json and manifest.json. While the changes are correct for a release, the pull request description is empty. For future releases, please consider filling out the description to provide context about the changes included in the release, which is helpful for tracking and understanding its purpose. I've also added a comment regarding an opportunity to improve the versioning process.
| { | ||
| "name": "promptbear-chrome-extension", | ||
| "version": "1.4.3", | ||
| "version": "1.4.5", |
There was a problem hiding this comment.
The version is updated here and also in manifest.json. I noticed the update_version.sh script in the repository, which seems intended to automate this process. However, the script currently only targets package.json files and appears to have a bug that would prevent it from working as expected. To make the release process more robust and less error-prone, I recommend fixing the update_version.sh script and extending it to also update the version in manifest.json. Automating this ensures version consistency across all relevant files with a single command.
Priority*
Purpose of the PR*
Changes*
How to check the feature
Reference