Skip to content

[chore] release 0.1.8#1090

Open
SolitaryThinker wants to merge 1 commit intomainfrom
will/release
Open

[chore] release 0.1.8#1090
SolitaryThinker wants to merge 1 commit intomainfrom
will/release

Conversation

@SolitaryThinker
Copy link
Collaborator

No description provided.

@SolitaryThinker SolitaryThinker added the go Trigger Buildkite CI label Feb 10, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @SolitaryThinker, 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 focuses on preparing for a new release by incrementing the project's version numbers across various configuration files. The primary impact is the update of the fastvideo package version, although an inconsistency exists between the version specified in the Python source file and the project metadata files.

Highlights

  • Version Update in fastvideo/version.py: The __version__ string in fastvideo/version.py was updated from "0.1.7" to "0.1.9".
  • Version Update in pyproject.toml: The project version in pyproject.toml was updated from "0.1.7" to "0.1.8".
  • Version Update in pyproject_other.toml: The project version in pyproject_other.toml was updated from "0.1.7" to "0.1.8".
  • Version Inconsistency Noted: A discrepancy was observed where fastvideo/version.py was updated to version 0.1.9, while pyproject.toml and pyproject_other.toml were updated to 0.1.8.

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

Changelog
  • fastvideo/version.py
    • Updated the internal __version__ string.
  • pyproject.toml
    • Updated the project's declared version.
  • pyproject_other.toml
    • Updated the project's declared version.
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 appears to be for releasing version 0.1.8, as indicated by the title and changes in pyproject.toml. However, there's a version inconsistency in fastvideo/version.py, which has been updated to 0.1.9. This mismatch is critical as it can lead to packaging and deployment issues. I've provided a suggestion to align the versions.

@@ -1 +1 @@
__version__ = "0.1.7"
__version__ = "0.1.9"
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

There is a version inconsistency. The pull request title and other configuration files (pyproject.toml, pyproject_other.toml) indicate a release version of 0.1.8, but this file has been updated to 0.1.9. To ensure a consistent and correct release, this version should be aligned with the others.

Suggested change
__version__ = "0.1.9"
__version__ = "0.1.8"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

go Trigger Buildkite CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant