# How to set the build revision

**URL:** <https://forums.balena.io/t/how-to-set-the-build-revision/345196>\
**Category:** balenaOS\
**Tags:** raspberrypi4\
**Created:** [August 23, 2021, 11:08pm UTC](https://forums.balena.io/t/how-to-set-the-build-revision/345196 "2021-08-23T23:08:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![0xff](https://avatars.discourse-cdn.com/v4/letter/0/5fc32e/32.png) [@0xff](https://forums.balena.io/u/0xff)\
**Post date:** [August 23, 2021, 11:08pm UTC](https://forums.balena.io/t/how-to-set-the-build-revision/345196/1 "2021-08-23T23:08:21Z")

</div>

The dashboard fleet releases page shows a `version` field. I’m sure this info must be online somewhere but I was unable to find out how to set this when I do a build so I have a better sense of what’s in a given build. Also, having a `notes` field that we could set with release or links would be great. Thanks.

---

<div class="post-metadata">

**Author:** ![thgreasi](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/thgreasi/32/454_2.png) [@thgreasi](https://forums.balena.io/u/thgreasi)\
**Post date:** [August 29, 2021, 1:42pm UTC](https://forums.balena.io/t/how-to-set-the-build-revision/345196/4 "2021-08-29T13:42:49Z")

</div>

Hi,  
The release version field that our dashboard started using recently is part of our work on providing a better versioning story to our users.  
We will be making a blog post and adding documentation about this once we have the last pieces in place. and will let you know once that happens.

In the mean time let me make a brief introduction on this.  
You can specify the version of a release that our dashboard presents, by adding a `balena.yml` file with a `version` field in the top level folder of your project, in which you run the `balena push`, `git push` or `balena deploy`commands to create a new release.  
For example a `balena.yml` could look like:

```auto
type: sw.application
version: '1.2.3'

```

The version field at the moment has to be in a 3-digit semver format and will be stored in the `release.semver` field in our backed. On top of that backend then will append the `+revN` for subsequent releases with the same version. The combined result of the base version you provided along with the autogenerated revision (in case the same version was used again earlier) will be available on the `release.version` field stored in our backed.

Let me also add that we do have plans to extend the current implementation to allow any valid semver value, including pre-release & build metadata parts.  
Let us know how that works for your use case.

I’ve also created an internal issue to track your request about adding a `release.notes` field and we will let you know once that becomes available.

Kind regards,  
Thodoris

---

<div class="post-metadata">

**Author:** ![0xff](https://avatars.discourse-cdn.com/v4/letter/0/5fc32e/32.png) [@0xff](https://forums.balena.io/u/0xff)\
**Post date:** [September 29, 2021, 12:01am UTC](https://forums.balena.io/t/how-to-set-the-build-revision/345196/6 "2021-09-29T00:01:33Z")

</div>

Hi @thgreasi - finally got to test this and it worked as advertised. Thank you!

Looking forward to getting the release.notes version.