I don't think this is a problem with git-flow, it's more a problem of using git-flow when you don't need it.
I use git-flow on projects that need to be installed by various different clients and there's no way to force all of them to migrate to the latest version, so you have to maintain support for older releases.
When the software needs to be installed in a single place and you can do it with CI/CD theres no need for the git-flow complexity.
I use git-flow on projects that need to be installed by various different clients and there's no way to force all of them to migrate to the latest version, so you have to maintain support for older releases.
When the software needs to be installed in a single place and you can do it with CI/CD theres no need for the git-flow complexity.