Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.4.0"
".": "0.4.1"
}
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [0.4.1](https://github.com/open-feature/cli/compare/v0.4.0...v0.4.1) (2026-03-26)


### 🐛 Bug Fixes

* **security:** update vulnerability-updates [security] ([#233](https://github.com/open-feature/cli/issues/233)) ([91ac14a](https://github.com/open-feature/cli/commit/91ac14ad40e0cbffbff87c1ac7cc3486fedf7c8c))
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

According to the repository's general rules, the full commit hash should be used for release builds to ensure clarity and avoid potential ambiguity. The current entry uses a short hash.

Suggested change
* **security:** update vulnerability-updates [security] ([#233](https://github.com/open-feature/cli/issues/233)) ([91ac14a](https://github.com/open-feature/cli/commit/91ac14ad40e0cbffbff87c1ac7cc3486fedf7c8c))
* **security:** update vulnerability-updates [security] ([#233](https://github.com/open-feature/cli/issues/233)) ([91ac14ad40e0cbffbff87c1ac7cc3486fedf7c8c](https://github.com/open-feature/cli/commit/91ac14ad40e0cbffbff87c1ac7cc3486fedf7c8c))
References
  1. Use the full commit hash for release builds and the short commit hash for development builds to differentiate them at a glance.


## [0.4.0](https://github.com/open-feature/cli/compare/v0.3.16...v0.4.0) (2026-03-09)


Expand Down
Loading