Skip to content

Conversation

openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

0.0.10 (2025-09-30)

✨ New Features

  • Angular SDK (#997) (105fd95)
  • angular: add Angular 18 support (#1063) (e62d6d4)
  • angular: add angular 19 to peerDependencies (4893d6f)
  • angular: add docs for setting evaluation context in angular (#1170) (24f1b23)
  • angular: add option for initial context injection (aafdb43)
  • support Angular 20 (#1220) (aa232a9)

🐛 Bug Fixes

🧹 Chore

📚 Documentation


This PR was generated with Release Please. See documentation.

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
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 serves as an automated release for version "0.0.10" of the OpenFeature Angular SDK. It consolidates a significant number of updates, including expanded Angular version compatibility (18, 19, 20), new capabilities like initial context injection, and various bug fixes and documentation enhancements. Notably, this release also corrects the version number in several project files, reverting it from "0.0.17" to the intended "0.0.10".

Highlights

  • Angular SDK Release: This pull request officially releases version "0.0.10" of the OpenFeature Angular SDK, incorporating a range of new features, bug fixes, and chore updates.
  • Version Correction: The release process involved updating the Angular SDK version from "0.0.17" to "0.0.10" across manifest, package, and README files, indicating a potential version correction or re-tagging.
  • New Features: Key new features include initial support for the Angular SDK, compatibility with Angular versions 18, 19, and 20, and the addition of an option for initial context injection.
  • Bug Fixes & Improvements: Several issues were addressed, such as fixing a race condition during initialization, ensuring correct license and package description in "package.json", and updating documentation.
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, appears to have a critical issue. It is attempting to downgrade the angular-sdk version from 0.0.17 to 0.0.10, which is against semantic versioning principles. This is reflected in package.json, .release-please-manifest.json, and README.md. Additionally, the CHANGELOG.md is being updated with a new, incorrect entry for 0.0.10 that has an invalid comparison link and aggregates changes from multiple previous versions, creating confusion and corrupting the release history. This suggests a significant error in the release automation configuration that should be addressed before merging.

"packages/server": "1.19.0",
"packages/shared": "1.9.1",
"packages/angular/projects/angular-sdk": "0.0.17"
"packages/angular/projects/angular-sdk": "0.0.10"
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 version for packages/angular/projects/angular-sdk is being downgraded from 0.0.17 to 0.0.10. This is inconsistent with semantic versioning and standard release practices. This appears to be an error in the release automation that needs to be corrected.

# Changelog


## [0.0.10](https://github.com/open-feature/js-sdk/compare/angular-sdk-v0.0.17...angular-sdk-v0.0.10) (2025-09-30)
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

This new release entry for version 0.0.10 is incorrect and will corrupt the project's release history for several reasons:

  • The comparison link .../compare/angular-sdk-v0.0.17...angular-sdk-v0.0.10 is invalid for a new release. It should compare the previous version to v0.0.10.
  • The changelog contents appear to be an aggregation of many previous versions, not just the changes for this specific release.
  • An entry for v0.0.10 already exists further down in this file.

This indicates a critical problem with the release automation that needs to be fixed.

{
"name": "@openfeature/angular-sdk",
"version": "0.0.17",
"version": "0.0.10",
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 package version is being downgraded from 0.0.17 to 0.0.10. According to semantic versioning, version numbers should be monotonically increasing. This is likely an error from the release automation and should be reverted.

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.

Beta release
2 participants