Erik,
The build instructions will build a version "v0.1-602-gb87733e" based on the deprecated "master" branch.
The most important info to be on track with your development is to type git checkout V4.3?before running make?(to build tinySA) or TARGET=F303 make?(to build tinySA4 aka. Ultra. Funny fact - at the moment you can set TARGET to every nonempty string to get the Ultra, also TARGET=F072 builds the Ultra version, see also my ).
BUT this will give a different version name "v1.2-658-g65f6118" (the g65f6118 correctly refers to the last commit on branch V4.3, but the v1.2-656 is out of order). See also?.?
My Q'n'D fix is to do this once after cloning:
? ? git tag -d v1.3
? ? git tag -a -m v1.3 v1.3 12a96bb
This matches your versioning and gives?v1.3-558-g65f6118 (at the time of my writing, you haven't pushed your latest commit 9ebab38, which is the base for??- have you?).
EDIT: I saw your two new commits, now GitHub is in front of your download page at version?v1.3-560-g88121a2. (real work in progress)
I hope this sheds some light on the mysteries of creating your own versions.
Martin
Ho-Ro