it's because there's a tag directly on master branch, I think
we shouldn't have a tag on master, right?
that's how it worked out
more commonly we don't because the release branch forks off
I think the "if commit is tagged, use that that tag for version" logic is not something we actually use anywhere
as a result we haven't actually thought through the edge cases
the actual problem here is that it uses the "most recent commit in that subdirectory" version which is a dev version for everything except api server for which it actually happens to be the tagged commit
but we don't build releases that way
I'm trying some things in 'version-at-commit.sh'
Congrats for 2.1.0 release! However, where can I find documentation regarding S3 compatible API?
@dantetwc I'm actually working on it right now and it'll be published in the next few days