Looks great, but for some reason it says that I run version 3.x instead of 3.2.1.
That means that, however you’re hosting farmOS, this line isn’t coming into play.
For instance, if you were using a development image or following the hosting with composer docs prior to this change, you would encounter that.
2 Likes
I do a combination of composer and the docker image, I install modules with composer but the farmos installation is done with the docker image.
So that might be why it says that but that is not really a problem, more of a observation.
2 Likes
Perhaps I should have also mentioned that this value comes directly from the API (/api @ .meta.farm.version) so my answers above aren’t really specific to Asset Link. i.e. They are also applicable to any (most?) other places the farmOS version is displayed - like the “Installation profile” line from /admin/reports/status.
1 Like
Yes, the farmOS version is set by this line in farm.info.yml: farmOS/farm.info.yml at 3b21346937cb48e54bfd280984c12399dfe54d95 · farmOS/farmOS · GitHub
That is always set to 3.x in the Git repository code, and our packaging scripts replace it with the actual version (from the Git tag). @Symbioquine linked to the relevant line in our build-farmOS.sh script.
However, if you are installing farmOS via Composer then that does not happen, so it always says 3.x.
We might be able to move that command to a Composer script that runs after composer install. That would probably solve this for all contexts. 
2 Likes