Hello team, It's sad that you can't use '@' in tags for something like "model-name@v0.1.2" You can create such tag, but it will give you "ref: invalid value: validation error" when you try to do something with it.

Sounds like a nasty bug. Would you mind submitting a bug report with full reproduction steps?

The list of allowed characters in a tag is limited, because some characters can be used in a ref expression. In this case, a

@

may appear after a branch name to mean "latest committed". So while your tag name would be unambiguous, we prohibit at-signs to avoid a tag named

model-name@

, which would be ambiguous with an expression meaning "the latest committed version of branch `model-name`". I realize that these rules can be frustrating in this case. You might still open that issue, perhaps we could still find a more open set of rules that would be less frustrating.

That's ok, no problem. Not allowing to create such tags is fine fix.