Skip to content

Comments

chore(main): release web-sdk 1.8.0#1354

Open
openfeaturebot wants to merge 1 commit intomainfrom
release-please--branches--main--components--web-sdk
Open

chore(main): release web-sdk 1.8.0#1354
openfeaturebot wants to merge 1 commit intomainfrom
release-please--branches--main--components--web-sdk

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

1.8.0 (2026-02-21)

✨ New Features

  • add "sideEffects": false to package.json files for all packages (#1343) (d8e968e)

Dependencies

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

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 automates the release of version 1.8.0 of the OpenFeature Web SDK. It incorporates a new feature that optimizes package bundling by marking side-effect-free modules and updates a core development dependency to its latest minor version.

Highlights

  • Web SDK Release: The OpenFeature Web SDK has been released as version 1.8.0.
  • New Feature: Added "sideEffects": false to package.json files for all packages, which can improve tree-shaking for bundlers.
  • Dependency Update: The @openfeature/core dev dependency has been bumped from ^1.9.2 to ^1.10.0.
Changelog
  • .release-please-manifest.json
    • Updated the packages/web entry to version 1.8.0.
  • packages/web/CHANGELOG.md
    • Added a new changelog entry for version 1.8.0, detailing the addition of sideEffects: false and the @openfeature/core dependency bump.
  • packages/web/README.md
    • Updated the release badge URL and version display to v1.8.0.
  • packages/web/package.json
    • Updated the package version to 1.8.0.
    • Updated the @openfeature/core dev dependency to ^1.10.0.
Activity
  • This pull request was automatically generated by the Release Please bot.
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 automates the release of web-sdk version 1.8.0. The changes primarily involve version bumps in package.json, CHANGELOG.md, and other metadata files. My review identified a potential dependency issue in packages/web/package.json where the peerDependencies for @openfeature/core has not been updated in line with the devDependencies, which could lead to compatibility problems for users of this SDK. I've left a specific comment with details.

},
"devDependencies": {
"@openfeature/core": "^1.9.2"
"@openfeature/core": "^1.10.0"
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.10.0, but the peerDependencies version for the same package remains ^1.9.2 (on line 53).

This can lead to issues if this new version of web-sdk relies on features introduced in @openfeature/[email protected], as consumers of this package might end up with an older, incompatible version of @openfeature/core.

According to the README.md:

Every SDK version has a requirement on a single, specific version of this dependency.

Please consider updating the peerDependencies to match the new requirement, for example to ^1.10.0, to ensure compatibility for consumers of this package.

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.

1 participant