Skip to content

Conversation

@thomaspoignant
Copy link
Member

This PR

Remove the release-as pinned to 1.0.0

Remove the release-as pinned to `1.0.0`

Signed-off-by: Thomas Poignant <[email protected]>
@thomaspoignant thomaspoignant requested review from a team as code owners December 4, 2025 14:14
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @thomaspoignant, 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 updates the project's release configuration by removing a specific release-as directive. This modification enables the automated release system to correctly increment versions beyond 1.0.0, ensuring that future releases reflect proper semantic versioning based on the project's commit history.

Highlights

  • Release Configuration Update: The release-as: "1.0.0" configuration has been removed from the root release-please-config.json file. This change allows the release process to automatically determine the next version based on conventional commits, rather than being pinned to 1.0.0.
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 removes the release-as: "1.0.0" configuration for the libs/providers/go-feature-flag package in the release-please-config.json file. This is a standard and correct cleanup action after a package has been bootstrapped to its initial major version, allowing release-please to manage subsequent versions automatically based on commit history. The change is straightforward and I see no issues.

@thomaspoignant thomaspoignant merged commit ee7eef3 into main Dec 4, 2025
7 checks passed
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