Skip to content

chore(main): release 0.3.15 #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
beeme1mr merged 1 commit into from
Feb 9, 2026
+14 −1
Merged

chore(main): release 0.3.15 #215

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .release-please-manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.3.14"
".": "0.3.15"
}
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
# Changelog

## [0.3.15](https://github.com/open-feature/cli/compare/v0.3.14...v0.3.15) (2026-02-09)


### 🐛 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))
Copy link

@gemini-code-assist gemini-code-assist bot Feb 9, 2026

Choose a reason for hiding this comment

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

medium

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
  1. 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))
Copy link

@gemini-code-assist gemini-code-assist bot Feb 9, 2026

Choose a reason for hiding this comment

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

medium

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.

* **main:** release 0.3.15 ([#211](https://github.com/open-feature/cli/issues/211)) ([9c5b634](https://github.com/open-feature/cli/commit/9c5b6345a4380438114a4e2b5c1e12839c55a43f))

## [0.3.14](https://github.com/open-feature/cli/compare/v0.3.13...v0.3.14) (2026-02-03)


Expand Down
Loading