# Version "unreleased"

**URL:** <https://discuss.ocaml.org/t/version-unreleased/8041>\
**Category:** Learning\
**Tags:** package, build\
**Created:** [June 22, 2021, 4:32pm UTC](https://discuss.ocaml.org/t/version-unreleased/8041 "2021-06-22T16:32:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ifazk](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/ifazk/32/836_2.png) [@ifazk](https://discuss.ocaml.org/u/ifazk)\
**Post date:** [June 22, 2021, 4:32pm UTC](https://discuss.ocaml.org/t/version-unreleased/8041/1 "2021-06-22T16:32:19Z")

</div>

I’ve seen a few projects with their main/trunk-branch hosting a package with a `.opam`/`dune-project` file listing the version as `unreleased`. Their CHANGES file also lists the changes from the last release listed under “unreleased”.

Is “unreleased” something that is recognized by any of the build/release tools that gets automatically updated when releasing the next version?

---

<div class="post-metadata">

**Author:** ![mefyl](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mefyl/32/2970_2.png) [@mefyl](https://discuss.ocaml.org/u/mefyl)\
**Post date:** [June 23, 2021, 8:44am UTC](https://discuss.ocaml.org/t/version-unreleased/8041/2 "2021-06-23T08:44:21Z")

</div>

For what it’s worth, “unreleased” is the suggested header for the section of the next release per [https://keepachangelog.com](https://keepachangelog.com). Since you’re not sure what the next version will be, it makes sense to not name it before then to avoid confusion. Not sure whether dune / opam do anything specific with it.

---

<div class="post-metadata">

**Author:** ![ifazk](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/ifazk/32/836_2.png) [@ifazk](https://discuss.ocaml.org/u/ifazk)\
**Post date:** [June 23, 2021, 8:49am UTC](https://discuss.ocaml.org/t/version-unreleased/8041/3 "2021-06-23T08:49:41Z")

</div>

Cool. Didn’t know about [https://keepachangelog.com](https://keepachangelog.com).