Thanks. I missed fixing this in the docs. The change to project.clj isn't important, I do that sort of randomly, but the other one is important, so thanks for catching this. It will be interesting to see what cljdoc does with this change. I may have to trigger a rebuild of the docs there, which I think I can do these days. Couldn't used to do that. For what it is worth, I go to a fair bit of trouble trying out cljdoc locally before I do a new release, since I think it is a cool thing. I also think cljdoc is cool because it uses zprint to format the API output.
Personally I have no problem with invalid version in project.clj, but it caused the build process to fail.
Hopefully, documentation build is the good target for automation too 😊
Thanks. I missed fixing this in the docs. The change to
project.clj
isn't important, I do that sort of randomly, but the other one is important, so thanks for catching this. It will be interesting to see whatcljdoc
does with this change. I may have to trigger a rebuild of the docs there, which I think I can do these days. Couldn't used to do that. For what it is worth, I go to a fair bit of trouble trying outcljdoc
locally before I do a new release, since I think it is a cool thing. I also thinkcljdoc
is cool because it uses zprint to format the API output.