chore(main): release 0.4.1

[openfeaturebot]

🤖 I have created a release beep boop

0.4.1 (2026-04-28)

🐛 Bug Fixes

• security: update vulnerability-updates [security] (#233) (91ac14a)
• security: update vulnerability-updates to v1.43.0 [security] (#237) (b96b303)

🧹 Chore

• align remaining Go 1.25 references in docs and test go.mod (#242) (e7e367d)
• deps: replace archived gopkg.in/yaml.v3 with go.yaml.in/yaml/v3 (#240) (1cf2beb)
• resolve open dependabot security alerts (#244) (1046097)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Code Review

This pull request increments the version to 0.4.1 and updates the changelog to include a security-related bug fix. The reviewer suggested using the full commit hash in the changelog entry for release builds to ensure clarity and consistency with repository standards.

[gemini-code-assist]

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.