SunVer
The version is the date. No encoding, no epoch, no math. Just the year, month-day, and time — written directly into X.Y.Z.
Formula
X = year
// 2026, 2027, …
Y = month × 100 + day // 101–1231
Z = hour × 100 + minute // 0–2359
Y = month × 100 + day // 101–1231
Z = hour × 100 + minute // 0–2359
X
year
YYYY
Y
101 – 1231
MMdd
Z
0 – 2359
HHmm
Examples
| Datetime | Version | How to read it |
|---|---|---|
| 2025-01-01 00:00 | 2025.101.0 | 2025, Jan 01, 00:00 |
| 2026-04-17 08:30 | 2026.417.830 | 2026, Apr 17, 08:30 |
| 2026-12-31 23:59 | 2026.1231.2359 | 2026, Dec 31, 23:59 |
| 2027-07-04 14:00 | 2027.704.1400 | 2027, Jul 04, 14:00 |
| 2030-06-01 00:00 | 2030.601.0 | 2030, Jun 01, 00:00 |
| 2033-08-20 12:00 | 2033.820.1200 | 2033, Aug 20, 12:00 |
| 2050-11-15 09:45 | 2050.1115.945 | 2050, Nov 15, 09:45 |
There's nothing to decode. 2026.417.830 is April 17th, 2026 at 08:30.
You just read it.
Converter
—
—
Properties
Monotonic sorting. Year, month+day, and time are each in their own
component in descending significance. Standard version comparison produces
chronological order.
No range limit. X is the year itself, so the scheme works for as long
as the Gregorian calendar does. No epoch, no overflow.
Minute resolution. Z = HHmm, so every minute is distinguishable.
Platform compatibility. X exceeds 255, so SunVer is
not compatible with Windows MSI installers. It works on macOS
(CFBundleVersion), Linux (deb/rpm), Android (versionName), iOS, NSIS, and
any system where version components can exceed 255. For MSI-constrained projects, use
MoonVer.