Don't add tags to ELPA packages -- documentation?

[Eric Abrahamsen]

I just realized that you can't realistically add tags to your ELPA
packages, because tag names need to be unique across a repo, and your
"v0.6" is going to conflict with other packages' attempts to tag the
same. EBDB occupied some prime tag real estate with its earlier point
versions, but now I can't tag 0.7 because eglot already has that.

Can I patch the README to tell developers not to use tags at all? (You
can't even tag locally and not push them; git still complains.) Or is
there any other trick to solve the situation?