@mckynzee and @franz, at this rate you may need to reconsider the numbering scheme - if a new release is issued every 18 days, that would be over 20 per year, and version 2 was out there for about two years if memory serves me correctly. So incrementing in .1’s could result in 3.40 in a couple of years which could easily be confused with 3.4 (full stop).
Another common choice is to have YYMM in the version.
So the initial March sprint would be 3.1803.0 then dot updates from there. July would be 3.1807.0. Next Feb 3.1902.0, etc… and the final number can increment with each build within the sprint.