chore(main): release 0.3.15 #215
Conversation
Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
Summary of ChangesHello @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 0.3.15, ensuring that the project's version manifest and changelog are accurately updated. The primary functional change included in this release is a fix for a .NET dependency injection issue within the generator. Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request is an automated release for version 0.3.15. It updates the .release-please-manifest.json file to reflect the new version and adds the corresponding changelog entries to CHANGELOG.md. While the core changes are standard for a release, there are a couple of points regarding the changelog content that could lead to confusion for users.
|
|
||
| ### 🐛 Bug Fixes | ||
|
|
||
| * **generator:** dotnet dependency injection issue ([#209](https://github.com/open-feature/cli/issues/209)) ([2cc23ee](https://github.com/open-feature/cli/commit/2cc23ee64c1bb009b0d858b0e79b52ed428bf22c)) |
There was a problem hiding this comment.
The general rules for this repository state that full commit hashes should be used for release builds to differentiate them from development builds. The commit hash 2cc23ee is a short hash, which goes against this guideline.
References
- Use the full commit hash for release builds and the short commit hash for development builds to differentiate them at a glance.
|
|
||
| ### 🧹 Chore | ||
|
|
||
| * downgrade version from 0.3.15 to 0.3.14 ([#214](https://github.com/open-feature/cli/issues/214)) ([32a1a40](https://github.com/open-feature/cli/commit/32a1a40d71a5cf0e1f6bc60697e10464438f45a8)) |
There was a problem hiding this comment.
Including a 'downgrade version from 0.3.15 to 0.3.14' entry within the 0.3.15 release notes can be confusing for users. This chore likely occurred before the 0.3.15 release was finalized, but its inclusion here makes it seem like a change within this release, which is not accurate. It might be clearer to exclude such pre-release internal chores from the final changelog presented to users, or rephrase it to indicate it was a rollback during development leading up to this release.
|
🤖 Release is at https://github.com/open-feature/cli/releases/tag/v0.3.15 🌻 |
2 participants
🤖 I have created a release beep boop
0.3.15 (2026-02-09)
🐛 Bug Fixes
🧹 Chore
This PR was generated with Release Please. See documentation.