chore(main): release nestjs-sdk 0.2.6

[openfeaturebot]

🤖 I have created a release beep boop

0.2.6 (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 * to 1.10.0
    • @openfeature/server-sdk bumped from 1.18.0 to 1.21.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 represents an automated release of the nestjs-sdk package, advancing its version to 0.2.6. The update incorporates a new feature aimed at optimizing package bundling by explicitly marking modules as side-effect free, alongside routine updates to key OpenFeature development dependencies.

Highlights

• New Feature: Added "sideEffects": false to package.json files across all packages, which can improve tree-shaking and optimize bundle sizes.
• Dependency Updates: Updated devDependencies for @openfeature/core to 1.10.0 and @openfeature/server-sdk to 1.21.0.
• Version Bump: The nestjs-sdk package has been released as version 0.2.6.

Changelog

• .release-please-manifest.json
  • Updated the version for packages/nest from 0.2.5 to 0.2.6.
• packages/nest/CHANGELOG.md
  • Added a new changelog entry for version 0.2.6, detailing the new sideEffects feature and updated dependencies.
• packages/nest/README.md
  • Updated the release badge URL and version to reflect v0.2.6.
• packages/nest/package.json
  • Updated the package version from 0.2.5 to 0.2.6.
  • Bumped @openfeature/core devDependency from * to 1.10.0.
  • Bumped @openfeature/server-sdk devDependency from 1.18.0 to 1.21.0.

Activity

• This pull request was automatically generated by the openfeaturebot using Release Please to manage the release process for the nestjs-sdk package.

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

This pull request, generated by release-please, prepares for the v0.2.6 release of the nestjs-sdk package. The changes primarily consist of version bumps in package.json, .release-please-manifest.json, and README.md, along with an updated CHANGELOG.md. The changes appear to be correct for an automated release, with one minor issue noted in the changelog regarding a future release date.

[gemini-code-assist]

The release date is set to a future date (2026-02-21). This appears to be an error. I noticed previous entries in this file also have future dates, which may indicate a systemic issue in the release automation's date generation that should be corrected.