Release version numbering is inconsistent, breaking automated version checking about superdirt

[yaxu]

Oops sorry for this typo! I was able to edit the existing release to fix the tag. Hopefully that's enough?

[telephon]

@alex et al, should we make a new release?

[cleary]

I'm unsure how the quarks in supercollider work for referencing specific versions, but if they use git tags would it be enough just to add a v1.7.3 tag at the same commit as v.1.7.3 without further work?

It just occurred to me that this version inconsistency also presents a problem for any documentation referencing the v1.7.2 format tag - people will be applying (and potentially updating documentation) the increment incorrectly in their configs.

[cleary]

oops, wasn't logged in - was wondering why I couldn't reply :P

that's done the trick.