coast-framework
Importing Coast as a deps project to Cursive can cause deps.edn auth failure
Under :aliases, the coast deps.edn has a couple of :git/url based dependencies with :sha verification hashes.
One thing that happens is that the shas can change on github when new releases happen there. The ones listed in a new coast project's deps.edn can then fail when importing a new deps project into cursive. The failure shows up as a cryptic 'Auth failure on deps.edn' message.
We've also observed that whether or not you see the failure depends on the previous deps installation history of the machine - so there's probably other state that is relevant to issue which I'm not aware of.
However, updating the deps.edn shas (or commenting those extra-deps out) does get around the issue and allow cursive to create the classpath correctly.
Just leaving this here in case anyone else hits the same problem.
