Skip to content

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

@openfeature/nestjs-sdk: 0.2.6

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @openfeature/server-sdk bumped from 1.18.0 to 1.20.1
@openfeature/react-sdk: 1.0.3

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @openfeature/web-sdk bumped from * to 1.7.2

This PR was generated with Release Please. See documentation.

@openfeaturebot openfeaturebot requested review from a team as code owners November 21, 2025 15:55
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @openfeaturebot, 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 an automated release generated by Release Please, which updates the versions of the @openfeature/nestjs-sdk and @openfeature/react-sdk. It also includes corresponding updates to their development dependencies, specifically bumping @openfeature/server-sdk for the NestJS SDK and @openfeature/web-sdk for the React SDK, ensuring these packages are up-to-date with their latest compatible versions.

Highlights

  • NestJS SDK Release: The @openfeature/nestjs-sdk has been released, bumping its version from 0.2.5 to 0.2.6.
  • React SDK Release: The @openfeature/react-sdk has been released, bumping its version from 1.0.2 to 1.0.3.
  • NestJS SDK Dependency Update: The @openfeature/server-sdk devDependency within the NestJS SDK has been updated from 1.18.0 to 1.20.1.
  • React SDK Dependency Update: The @openfeature/web-sdk devDependency within the React SDK has been updated from * to 1.7.2.
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, generated by Release Please, prepares new releases for @openfeature/nestjs-sdk (v0.2.6) and @openfeature/react-sdk (v1.0.3). The changes include version bumps in package.json files and updates to the changelogs. However, I've identified a critical issue where devDependencies in both updated packages are being pinned to versions of other workspace packages that are not being released in this PR and do not seem to exist. This will likely cause dependency installation to fail and should be addressed before merging.

"@nestjs/testing": "^11.0.20",
"@openfeature/core": "*",
"@openfeature/server-sdk": "1.18.0",
"@openfeature/server-sdk": "1.20.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

The devDependency on @openfeature/server-sdk is being updated to version 1.20.1. However, based on the files in this pull request and the repository context, the latest version of @openfeature/server-sdk appears to be 1.20.0, and it is not being updated as part of this release. This will likely cause dependency resolution to fail. Please ensure that the dependency versions are correct and point to existing or soon-to-be-published versions within this same release.

"devDependencies": {
"@openfeature/core": "*",
"@openfeature/web-sdk": "*"
"@openfeature/web-sdk": "1.7.2"
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

The devDependency on @openfeature/web-sdk is being updated from * to 1.7.2. While pinning dependencies is a good practice, the version 1.7.2 of @openfeature/web-sdk does not seem to exist within this pull request's context. The current version appears to be 1.7.1, and it's not being updated in this release. This will likely break dependency installation. Please verify the target version.

@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch 2 times, most recently from a73bcb5 to 82637a2 Compare November 26, 2025 17:33
Signed-off-by: OpenFeature Bot <[email protected]>
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main branch from 82637a2 to 26d8ded Compare November 26, 2025 18:37
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