diff --git a/.changeset/fix-fragment-children.md b/.changeset/fix-fragment-children.md
deleted file mode 100644
index 16d51cb..0000000
--- a/.changeset/fix-fragment-children.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"eslint-plugin-react-render-types": patch
----
-
-fix: validate children inside JSX fragments in `valid-render-prop` rule
-
-Previously, components wrapped in JSX fragments (`<>...</>`) were silently skipped during children validation. This meant neither valid nor invalid children inside fragments were checked against `@renders` annotations. Now fragments are recursively unwrapped in both `validateJSXChildren` and `extractChildElementNames`.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3a5c884..0b9e11d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
 # eslint-plugin-react-render-types
 
+## 0.7.5
+
+### Patch Changes
+
+- [#23](https://github.com/HorusGoul/eslint-plugin-react-render-types/pull/23) [`ab12d88`](https://github.com/HorusGoul/eslint-plugin-react-render-types/commit/ab12d88e98ef62480b2703d16ebf096d502122b2) Thanks [@HorusGoul](https://github.com/HorusGoul)! - fix: validate children inside JSX fragments in `valid-render-prop` rule
+
+  Previously, components wrapped in JSX fragments (`<>...</>`) were silently skipped during children validation. This meant neither valid nor invalid children inside fragments were checked against `@renders` annotations. Now fragments are recursively unwrapped in both `validateJSXChildren` and `extractChildElementNames`.
+
 ## 0.7.4
 
 ### Patch Changes
diff --git a/package.json b/package.json
index fae6b3e..fbf646f 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-react-render-types",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "type": "module",
   "description": "ESLint plugin that brings Flow's Render Types to TypeScript via JSDoc comments",
   "main": "dist/index.js",