# Proper semver versioning, at least for Athom apps **URL:** \ **Category:** Developers\ **Created:** [October 10, 2018, 7:49pm UTC](https://community.homey.app/t/proper-semver-versioning-at-least-for-athom-apps/2681 "2018-10-10T19:49:54Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [October 10, 2018, 7:49pm UTC](https://community.homey.app/t/proper-semver-versioning-at-least-for-athom-apps/2681/1 "2018-10-10T19:49:54Z")
Even though [the fine manual](https://developer.athom.com/docs/apps/tutorial-App%20Manifest.html) states that app should use _“a Semantic Version”_, linking to [semver.org](http://semver.org), it seems that most developers, including Athom, don’t actually use the SemVer rules that come with proper semantic versioning. Case in point: a new version for the KaKu app [with known incompatible changes](https://community.homey.app/t/klikaanklikuit-by-athom/81/42) that just got a patch version increase, from 4.0.13 to 4.0.14. With proper semver versioning, app updates could become so much better. Users could choose which types of automatic updates they would prefer: - any, including (possible) incompatible changes - updates including new features, but only when the changes won’t lead to (possible) incompatibilities - bugfixes only It would also provide developers with an incentive to adopt proper semantic versioning. Right now, I don’t think most developers use a consistent versioning scheme for their apps. ---
**Author:** ![cbh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cbh/32/13668_2.png) [@cbh](https://community.homey.app/u/cbh)\ **Post date:** [October 11, 2018, 6:47am UTC](https://community.homey.app/t/proper-semver-versioning-at-least-for-athom-apps/2681/2 "2018-10-11T06:47:13Z")
Or at least a _dated_ changelog - also for Athom apps (part of proper versioning, of course)