Fork me on GitHub
Joshua Suskalo13:07:22

Maybe something else to be considered is releasing a -T tool which can be run that would start a build of the cljdoc documentation using the current sha (which may not match the tag) and an argument for what tag the release corresponds to.


Yeah, I found that I already have a bad SHA in the cljdoc version of depstar's docs and I have no way to fix it now 😐


Right… Interesting. So when docs are updated to reference a release sha, they aren’t part of the release because the doc update is the next commit. I remember being a bit confused about how cljdoc treated tag version vs sha, I’ll see if I can find some old notes.