From 57f02ead0ae3afce66180d7f7c3c84dac9a150e1 Mon Sep 17 00:00:00 2001
From: Gaspard Kirira <gaspardkirira9@gmail.com>
Date: Sat, 21 Feb 2026 10:53:37 +0300
Subject: [PATCH] v1.36.2: fix publish registry versions field

---
 CHANGELOG.md | 30 ++++++++++++++++++++++++++++++
 modules/cli  |  2 +-
 2 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 153d55a..df1372e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,6 +8,36 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ---
 
 ## [Unreleased]
+## v1.36.2
+
+### Fix
+
+- **publish**: always include published version (`tag` + `commit`) inside registry entry `versions` field
+
+### Why
+
+Registry validation requires a non-empty `versions` object.
+
+Previously, `vix publish` created a registry entry with:
+
+```json
+{
+  "versions": {}
+}
+```
+
+This caused the `validate_registry_pr` workflow to fail before auto-merge.
+
+### Result
+
+- Registry PRs are now immediately valid
+- Auto-merge works reliably without manual intervention
+- No need to manually patch `index/*.json`
+- `registry_index_from_tags` remains compatible
+
+### Impact
+
+Publishing a new library version is now fully automated and stable.
 ## v1.36.1
 
 ### Improvements
diff --git a/modules/cli b/modules/cli
index f914ed7..fe48193 160000
--- a/modules/cli
+++ b/modules/cli
@@ -1 +1 @@
-Subproject commit f914ed738d47e6ac1e2688a6632a1f79733f3323
+Subproject commit fe48193837bca9ce2c3522936c9122fc49c5e52f