This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-23
Channels
- # announcements (66)
- # babashka (41)
- # beginners (93)
- # calva (10)
- # cider (2)
- # clj-kondo (112)
- # cljs-dev (6)
- # cljsrn (1)
- # clojure (44)
- # clojure-dev (10)
- # clojure-europe (35)
- # clojure-italy (15)
- # clojure-nl (3)
- # clojure-uk (2)
- # clojurescript (38)
- # conjure (1)
- # datalevin (1)
- # datomic (16)
- # deps-new (4)
- # events (7)
- # figwheel-main (1)
- # fulcro (59)
- # graalvm (21)
- # integrant (3)
- # introduce-yourself (8)
- # jobs-discuss (2)
- # malli (23)
- # membrane (11)
- # membrane-term (2)
- # missionary (17)
- # off-topic (7)
- # pathom (23)
- # pedestal (6)
- # polylith (7)
- # portal (25)
- # releases (1)
- # remote-jobs (3)
- # reveal (5)
- # shadow-cljs (43)
- # spacemacs (7)
- # sql (18)
- # tools-deps (33)
- # vim (10)
- # xtdb (36)
måning!
I don't think there's really a need to release as mvn dep anymore if your lib is purely source based, you can mark a git dep as stable using a tag
But if your lib contains .class files for example, you typically don't check these into source control (but some do)
From the maintainers side I tend to agree, but what about immutability and trust? GitHub Repos can be deleted, Tags can be moved :thinking_face:
Commit Hashes are fixed, of course
> When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
that'd exclude all the lein users (the majority of clojure users), I personally always deploy to clojars
in some context there are also super strict vetting rules, ex: can't pull anything from the outside world unless it's audited. Very often process exist for mvn hosted artifacts (ex mirroring), with git based deps it requires a bit more work to setup, it's not that bad but you end up having to maintain both