Skip to content

fix: issues reported by releasekit#4646

Merged
yesudeep merged 1 commit intomainfrom
yesudeep/fix/spicy-sun
Feb 13, 2026
Merged

fix: issues reported by releasekit#4646
yesudeep merged 1 commit intomainfrom
yesudeep/fix/spicy-sun

Conversation

@yesudeep
Copy link
Contributor

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yesudeep, 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 addresses issues identified by releasekit by systematically updating the metadata for various Python plugins. The changes primarily focus on preparing several community plugins for release by adjusting their pyproject.toml configurations to mark them as publishable and include essential links like changelogs and READMEs. Concurrently, the releasekit configuration itself has been enhanced with more detailed repository information and refined plugin categorization. A crucial internal improvement to releasekit ensures that package publishability status is accurately reflected and updated during the fixing process, preventing stale data from affecting subsequent operations.

Highlights

  • Plugin Publishability: Several community plugins (amazon-bedrock, cloudflare-workers-ai, cohere, deepseek, huggingface, microsoft-foundry, mistral, xai) have been updated to be publishable by removing the 'Private :: Do Not Upload' classifier from their pyproject.toml files.
  • Metadata Enrichment: For the newly publishable plugins, Changelog URLs have been added to their pyproject.toml files. Additionally, readme = "README.md" was added for the Cohere, DeepSeek, Hugging Face, and Mistral plugins.
  • Plugin Reclassification: The releasekit.toml configuration was updated to move the previously unreleased plugins into the community_plugins group. Conversely, the checks plugin was moved to unreleased_plugins, and dev-local-vectorstore was explicitly added to internal_tools.
  • Releasekit Configuration Update: The releasekit.toml file now includes more explicit repository and package identification settings, such as forge, repo_owner, repo_name, core_package, plugin_prefix, namespace_dirs, library_dirs, and plugin_dirs.
  • Releasekit Internal Logic Improvement: A new internal function _refresh_publishable was added to releasekit to re-evaluate a package's publishability status from its pyproject.toml after metadata changes. This ensures that subsequent fixers operate on the most current is_publishable state.

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

@yesudeep yesudeep enabled auto-merge (squash) February 13, 2026 04:15
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 updates the releasekit configuration and tooling to prepare several plugins for public release. The changes are consistent across pyproject.toml files and the main releasekit.toml configuration. A new function _refresh_publishable is introduced to ensure package metadata is up-to-date in memory after being modified on disk, which is a good addition for robustness. My only suggestion is to improve error handling in this new function by logging exceptions instead of silently ignoring them.

@yesudeep yesudeep force-pushed the yesudeep/fix/spicy-sun branch from 9998778 to 7f61cd9 Compare February 13, 2026 04:24
@yesudeep yesudeep merged commit fba9ed1 into main Feb 13, 2026
21 checks passed
@yesudeep yesudeep deleted the yesudeep/fix/spicy-sun branch February 13, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants