Skip to content

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

1.7.3 (2026-01-29)

🔄 Refactoring

  • move Multi-Provider shared code to core package (#1324) (baf33f0)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @openfeature/core bumped from ^1.9.0 to ^1.9.2

This PR was generated with Release Please. See documentation.

Signed-off-by: OpenFeature Bot <[email protected]>
@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 represents an automated release for the OpenFeature Web-SDK, advancing its version to 1.7.3. The update primarily incorporates a refactoring change that relocates shared Multi-Provider code into the core package, alongside a minor update to a development dependency. This ensures the Web-SDK remains current and benefits from shared core functionalities.

Highlights

  • Web-SDK Release: The OpenFeature Web-SDK has been released as version 1.7.3.
  • Refactoring: Shared Multi-Provider code has been moved to the core package to improve modularity and reusability.
  • Dependency Update: The development dependency for @openfeature/core has been updated from ^1.9.0 to ^1.9.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 is for the release of web-sdk version 1.7.3. The changes are mainly version bumps and documentation updates, which appear to be standard for a release. However, I've noticed a potential issue with the peerDependencies configuration in packages/web/package.json. While a devDependency is updated, the corresponding peerDependency is not, which could cause issues for users of this package. Please see my specific comment for details.

Comment on lines 55 to 57
"devDependencies": {
"@openfeature/core": "^1.9.0"
"@openfeature/core": "^1.9.2"
}
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The devDependencies for @openfeature/core is being updated to ^1.9.2, but the peerDependencies version for it on line 53 remains ^1.9.0. The changelog indicates that multi-provider code was moved to the core package, which likely means this SDK now requires a newer version of @openfeature/core.

To prevent potential runtime errors for consumers of this package, the peerDependencies should be updated to reflect the new minimum required version. If features from @openfeature/[email protected] are now necessary, the peerDependencies should be bumped to ^1.9.2.

Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

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

Due to #1324, we will have to update the minimum core version to 1.9.2 so that references from this SDK to core do not break.

I will do this manually on release.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants