From 78f7301a0d545e2393b3ae7a4ab5e324c0be1629 Mon Sep 17 00:00:00 2001
From: RayPals <raypals@noreply.codeberg.org>
Date: Mon, 1 Jun 2026 00:53:40 +0200
Subject: [PATCH] Add docs/VERSIONING.md from Claro v1.17.26 zip

---
 docs/VERSIONING.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 docs/VERSIONING.md

diff --git a/docs/VERSIONING.md b/docs/VERSIONING.md
new file mode 100644
index 0000000..9b479b1
--- /dev/null
+++ b/docs/VERSIONING.md
@@ -0,0 +1,31 @@
+# Claro Versioning
+
+Claro uses visible versions in this format:
+
+```text
+v1.xx.yy
+```
+
+Meaning:
+
+```text
+v1 = overall major version
+xx = revision / release number
+yy = year
+```
+
+Example:
+
+```text
+Claro v1.15.26
+```
+
+That means:
+
+```text
+major version: 1
+revision:      10
+year:          2026
+```
+
+Normal Claro development should stay in the `v1` line. A future `Claro v2` should mean an entire rewrite many years later, not a normal feature update.