#TFW the appropriate response to a tool in your build chain going out of support is to just... Delete it, without replacement.
If there's one lesson I've learned from working on this demon-haunted codebase, it's *don't* modernize your tooling unless you're actually prepared to commit to hunting down and completely decommissioning whatever you're replacing.
Also, really genuinely consider whether you need a tool to generate a config file from your codebase, or whether maaaaaybe it will actually be easier in the longrun to just maintain a config file.
@Nentuaby I'm currently dealing with an issue similar to this in my 2005-vintage codebase. Because of automation and custom frameworks that we've standardized on, we're stuck on old libraries, and security is poking at us now to upgrade from these vulnerable dependency versions.
I'm beginning to develop a nervous tic now, that triggers a disgust reaction when I hear things like "automation" and "code generation" :).
