This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-30
Channels
- # announcements (31)
- # aws (17)
- # babashka (26)
- # babashka-sci-dev (8)
- # beginners (16)
- # biff (1)
- # calva (9)
- # cider (5)
- # clj-kondo (3)
- # clj-on-windows (38)
- # cljdoc (2)
- # cljs-dev (9)
- # cljsrn (6)
- # clojure (58)
- # clojure-europe (47)
- # clojure-nl (3)
- # clojure-norway (21)
- # clojure-uk (2)
- # clojurescript (25)
- # conjure (2)
- # data-science (7)
- # datomic (3)
- # emacs (12)
- # events (5)
- # fulcro (5)
- # honeysql (10)
- # introduce-yourself (7)
- # lsp (4)
- # meander (3)
- # nbb (18)
- # off-topic (28)
- # rdf (1)
- # releases (2)
- # sci (5)
- # shadow-cljs (23)
- # sql (5)
- # test-check (3)
are there any helpful tools for updating aws-api libs like > update! ssm 823 -> 834? (y/n) y! .....823 -> 834
asking bc i'm about to write one unless someone else jumps in.
yeah, but the aws-api latest-release isn't a deps.edn file at the project root, so it wouldn't know to compare it against your deps..
though i guess i can just make it into one then run the tool lol.
that will probably be harder though honestly.
ah right, antq just quickly came to my mind, thought that looking up latest libs in maven would be enough :)
oh cool. the aws libs don't even follow semantic versioning.
so this semvar library i wanted to use doesn't work. Why are we using strings to carry information separated by dots. why is everything not clojure data structures?
A formatted string is easy to type and read for humans, a "version" is just an identifier, an awfully small piece of data to express possibly a big lot of information, with human interpretation in the middle
i guess i can probably write a recursive compare function
I wonder what/who creates/maintains that latest-releases.edn file, seems that it is used to update other resources in the repo (readme, libs under the examples alias in deps.edn file in the repo)
I think the released libs have to have been pushed to maven central before updating the latest-releases.edn end file, since otherwise the clj -A:examples
example wont work
for just for moving to the latest version of all libs I think looking up the current latest artifact in maven central via antq (for Leiningen only there used to be lein-ancient I think?) should be enough, if I'm on the right track 🙂
Here i wrote these helper functions to do the update on a deps file. I doubt ill ever use them, but i was tired of not doing things. https://github.com/drewverlee/aws-api-lib-crudanator/blob/e5a80060a782e4417920ca04acae1c2ec2b75294/src/drewverlee/aws_api_lib_crudanator.clj#L75