Going forward, the application feed is going to automatically remove any template within a template Repository that:
Refers to the exact same dockerHub repository as another template within the same repository AND
Has the exact same application name as the other template
Currently Apps falling into this are hard to find because everything "looks right" until you actually go to install one of them (and even there it still "looks" right even though it's not and the wrong template gets installed
This rare situation to be handled otherwise requires a major overhaul (Read that as a full day's work in overhauling CA, and basically starting the ENTIRE QA process in CA all over again (ie: Months of regression testing)
IMO, the ideal way to handle this type of stuff from a Maintainer's side is to use CA's Branches, but I do understand why authors don't always want to integrate branches.
@hernandito