Skip to content

fix: remove $schema field from .release-please-manifest.json#87

Merged
oxddr merged 1 commit intoopen-feature:mainfrom
oxddr:release-please-fix
Mar 12, 2026
Merged

fix: remove $schema field from .release-please-manifest.json#87
oxddr merged 1 commit intoopen-feature:mainfrom
oxddr:release-please-fix

Conversation

@oxddr
Copy link
Contributor

@oxddr oxddr commented Mar 12, 2026

Remove $schema field from .release-please-manifest.json to fix broken release-please config.

@oxddr oxddr requested review from a team as code owners March 12, 2026 09:42
@gemini-code-assist
Copy link

Summary of Changes

Hello, 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 an issue with the release-please configuration by removing a problematic "$schema" field from the manifest file. This change ensures the proper functioning of the automated release process, preventing potential errors and allowing for smooth version management.

Highlights

  • Configuration Fix: Removed the "$schema" field from .release-please-manifest.json to resolve a broken release-please configuration.
Changelog
  • .release-please-manifest.json
    • Removed the "$schema" field.
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.

Signed-off-by: Janek Łukaszewicz <janluk@google.com>
@oxddr oxddr force-pushed the release-please-fix branch from c1207a1 to 2a5027e Compare March 12, 2026 09:42
@oxddr oxddr requested a review from NeaguGeorgiana23 March 12, 2026 09:42
Copy link

@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 fixes a broken release-please configuration by removing the $schema field from the .release-please-manifest.json file. The change correctly addresses the described issue. I have included one suggestion to improve the formatting of the JSON file by removing an unnecessary blank line.

@oxddr oxddr merged commit 28c283c into open-feature:main Mar 12, 2026
4 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