Confusing behavior (bug?) v0.0.0 fallback code does not work if there are *any* tags in the repo

[jfly]

Confusing behavior (bug?) v0.0.0 fallback code does not work if there are *any* tags in the repo

[mtkennerly]

Thanks for the detailed ticket!

I think option 1 makes sense. "There are no tags" and "there are no tags that match the pattern" aren't all that different, and we can extend --strict to preserve the current error.

Regarding potential breakage:

• Since this only applies before you have a version tag, the scope is pretty small.
• If you handle the current error, then you'd probably set a fallback version as well.
• If you prefer a different fallback version than 0.0.0, then you already have to check if Dunamai gives you 0.0.0 so you can use something else instead, since we use 0.0.0 in several other cases.
• If you're worried about cases where CI doesn't have the full history and only fetches a subset of tags (possibly not including any version-like tags), then you should be using --strict.