The version tags should take the form package-name-v<major>.<minor>.<patch>, and presumably package-name-v0.<major>.<minor>+<patch> if they're below 1.0.0 to match pub.

It would be ideal if this could be handled by our CI somehow. We've already struggled to remember to increment the pubspec consistently, I think remembering to create and push git tags is going to be even more error prone. Could be some Cirrus script that tags commits on master correctly if the pubspec has been changed? The script itself sounds easy enough to write, but I don't know if it's a great idea to give our CI the ability to push tags. Is there even an already existing Github bot for this we could pull in, or maybe we could write our own?

/cc @csells @amirh @collinjackson