Overwriting a tag would constitute:

```js
1) removing said remote tag
2) removing said local tag
3) creating the new tag
4) pushing this tag to the endpoint
```

Now, you can take this algorithm, and optionally insert a step 0, which would clobber all of the tags matching a given pattern, if a specific command line flag or option is set.

I think this is reasonable --- `overwriteVersion` does essentially what it says it's doing (where `version` refers to a `tagged version`, specifically, and so just a single tag). The option could even be renamed to `overwriteTag`.

The second option could be called whatever you like, really, `clobberSimilarTags`, `clobberVersionTags`, or some creative name for it.

I agree that 2-tags isn't necessarily the easiest way to use this, but `overwriteVersion` is really a misleading name for something which actually destroys any number of "versions" if they start with the same prefix, so if we want it to do that, we need either a better name for it, or another option to compound it into behaving that way.

Which would you see as the preferred API?