Working around invalid tag formats?

[AndrewLeedham]

I am working on converting a project from semantic-release to Auto. A process I have done a few times in the past. But running into some interesting issues this time, the project in question uses a custom tag format of <env>-x.x.x e.g dev-1.431.0 or prod-1.164.0. This is causing issues because Auto does not recognise this format and throws errors when trying to get the version number from them. I am trying to find a work around that does not involve changing all the tags, because I won't be updating to Auto across all environments (dev/stage/prod) straight away.

So far I have tried a few things:

• Adding valid versions to the latest commit, Auto seems to traverse all tags, so it fails if any don't match!
• Creating a custom git-tag plugin which parses this new format. However, it seems Auto still does tag processing internally regardless of release plugins.

Any ideas or thoughts would be greatly appreciated?