This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-27
Channels
- # announcements (3)
- # babashka (16)
- # beginners (177)
- # calva (102)
- # cider (2)
- # clj-kondo (12)
- # clojars (10)
- # clojure (91)
- # clojure-argentina (3)
- # clojure-australia (5)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-uk (10)
- # clojurescript (73)
- # community-development (8)
- # cursive (9)
- # depstar (7)
- # fulcro (5)
- # helix (1)
- # introduce-yourself (1)
- # jobs-discuss (18)
- # lsp (32)
- # luminus (1)
- # malli (2)
- # music (4)
- # off-topic (20)
- # pathom (19)
- # polylith (15)
- # re-frame (4)
- # reagent (6)
- # ring (13)
- # sci (36)
- # shadow-cljs (7)
- # spacemacs (4)
- # sql (3)
- # tools-deps (112)
- # vim (21)
hi. I am following the guide
and using the suggested depstar coordinates {:tag "v2.1.267" :sha "a970a33"}
and i am receiving the error
> Library com.github.seancorfield/depstar has sha and tag that point to different commits
It seems the tag v2.1.267
is on commit 1a45f79
with message "prep for 2.1.267". The sha a970a33
is on tag v2.1.253
Yeah, http://cljdoc.org builds from the tag and there's no way you can update the sha afterward. Sorry about that. I've raised the issue with cljdoc folks
In the next release, I'm going to link back to the "live" CHANGELOG on GitHub and have the short sha next to each tag in the releases there.
(since I can update the change log on GH after I tag the release)
I didn't realize it was up on cljdoc like that until it was too late 😞
I've got enough changes to cut a new release. I just need to finesse the docs before I do that...