Lots of scrollback I didn’t read in detail. But the reason we are pulling an ezbake branch during build is purely because we didn’t have it set up to push to clojars when I wrote it and I was making changes frequently and wanted to pull them down immediately. When we are in a stable place, we should definitely be pushing the version to clojars and letting lein pull it down.
As for clj-parent, it’s a little tricky. It’s used in more than 2 things we need. For example, it’s used for trapperkeeper, jvm-ssl-utils, a bunch of the puppet/perforce-written dependencies used within server/db. In fact, it’s used in pretty much all of them. We could unwind it and put them all in each project specifically, and maybe that’s okay if you end up using renovate to manage them all. But I think the point of clj-parent was to make an easy way to do it in one place but also a way to version that whole set of dependencies so that it’s common across projects. And also to support different sets of versions for different branches (e.g. puppet 7 vs 8)