There have always been renewals. It's just not commonly used because the majority of files charge the cost upfront instead of letting you spread it over a period of time. If used correctly, renewals are a fantastic way to keep initial costs down. But if used incorrectly, they would turn people off from buying your file.
I imagine you're here because of Drug Deals, and this would be the way you don't do renewals. But it's better to let them make the mistake on their own and learn from it instead of trying to force them to use a specific pricing structure. Chances are that renewal is going to go away once they see all the pushback from it.
It's important to note that renewals are not really subscriptions. You don't have to renew and still maintain access to the version you initially purchased. This is just a way for developers to charge for updates rather than force someone to pay a lump sum right out of the gate. Again, it's to reduce the cost of entry, not add an idiot tax. If authors use it in that manner, then they'll get called out, which is exactly what's happening.
We'd rather not remove renewals just because a handful of people use them incorrectly. It's a very valuable feature and opens the door for more SAAS to be integrated directly into Codefling. Of course, if we ever start shifting into SAAS primarily for plugins, then I wouldn't hesitate to remove the feature to maintain the integrity of the platform.