# 3.2.1 is not a "clean" version commit

**URL:** <https://meta.discourse.org/t/3-2-1-is-not-a-clean-version-commit/299518>\
**Category:** Product Support\
**Created:** [March 15, 2024, 12:36pm UTC](https://meta.discourse.org/t/3-2-1-is-not-a-clean-version-commit/299518 "2024-03-15T12:36:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Arkshine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arkshine/32/298682_2.png) [@Arkshine](https://meta.discourse.org/u/Arkshine)\
**Post date:** [March 15, 2024, 1:50pm UTC](https://meta.discourse.org/t/3-2-1-is-not-a-clean-version-commit/299518/3 "2024-03-15T13:50:48Z")

</div>

In my understanding, `v3.2.0 +9` +9 means a few commits are available on top of your current version (before 3.2.1)

`v3.2.1 +5` would mean you can update to the next version, 3.2.1, and a few commits have already been added on top of this version. Usually, I believe that would be important fixes backported from the main branch.

I understand that could be confusing a first. I’m wondering if this could be improved. 🤔

---

_[View the full topic](https://meta.discourse.org/t/3-2-1-is-not-a-clean-version-commit/299518)._