chore(main): release react-sdk 1.3.0

[openfeaturebot]

🤖 I have created a release beep boop

1.3.0 (2026-03-31)

✨ New Features

• add "sideEffects": false to package.json files for all packages (#1343) (d8e968e)
• support type-safe flag keys via module augmentation (#1349) (fb2ed4a)

Dependencies

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

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Summary of Changes

Hello @openfeaturebot, I'm Gemini Code Assist¹! 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 @openfeature/react-sdk version 1.3.0. It incorporates a new feature that adds "sideEffects": false to package.json files to improve tree-shaking capabilities for bundlers. Additionally, it updates several development dependencies to their latest stable versions.

Highlights

• New Feature: Added "sideEffects": false to package.json files for all packages, which can help bundlers with tree-shaking.
• Dependency Updates: Bumped @openfeature/core from * to 1.10.0 and @openfeature/web-sdk from * to 1.8.0 in dev dependencies.
• Release: Released @openfeature/react-sdk version 1.3.0.

Changelog

• .release-please-manifest.json
  • Updated the version of packages/react from 1.2.1 to 1.3.0.
• packages/react/CHANGELOG.md
  • Added a new entry for version 1.3.0.
  • Included a new feature: add "sideEffects": false to package.json files for all packages.
  • Documented dependency updates for @openfeature/core and @openfeature/web-sdk.
• packages/react/README.md
  • Updated the release badge URL and version display from v1.2.1 to v1.3.0.
• packages/react/package.json
  • Updated the package version from 1.2.1 to 1.3.0.
  • Updated devDependencies for @openfeature/core to 1.10.0 and @openfeature/web-sdk to 1.8.0.

Activity

• The pull request was automatically generated by Release Please.

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

[gemini-code-assist]

Code Review

The pull request prepares the release of @openfeature/react-sdk version 1.3.0. The primary concern is the update of devDependencies in packages/react/package.json to versions of @openfeature/core and @openfeature/web-sdk that do not currently exist in the repository. This mismatch will likely lead to broken builds and installation errors. On a positive note, the inclusion of "sideEffects": false in the package.json files is a good improvement for tree-shaking.

[gemini-code-assist]

The devDependencies for @openfeature/core and @openfeature/web-sdk are being updated to 1.10.0 and 1.8.0. However, the current versions in the repository are 1.9.2 and 1.7.3. If these new versions haven't been published to NPM yet, npm install will fail. It's generally safer in a monorepo to use the current workspace versions or the * wildcard for internal dev dependencies.

Suggested change

	"@openfeature/core": "1.10.0",
	"@openfeature/web-sdk": "1.8.0"
	"@openfeature/core": "1.9.2",
	"@openfeature/web-sdk": "1.7.3"