Clojurians Log v2
clj-commons
I merged PR #24 on durable-queue -- looks like this library got dropped on the floor after the transfer to clj-commons. It seems to be set up for CircleCI testing but not GitHub Actions and in order to make new releases, we'll have to publish to clj-commons/durable-queue since we don't have access to the Factual group on Clojars. I might noodle around on it for the next couple of days to see if I can get some issues triaged and PRs merged (or rejected). I'd much prefer to use GH Actions, since I haven't used CircleCI for ages.
I removed the webhook that was kicking off jobs on CircleCI. Took me a while to remember that's how the integration worked!
org.clj-commons/durable-queue {:mvn/version "0.1.7"} is now available! I'll post to #announcements
A note on this work: although I removed the (broken) CircleCI integration (I removed the .yml file but I suspect something may also need doing at CircleCI so it stops watching the repo?), I left the old project.clj file in place because there are a couple of bits that are not yet replicated to the newer infrastructure (e.g., codox -- which was last run to create gh-pages back for v0.1.2(!): https://clj-commons.org/durable-queue/ )
Cool. I can also look into cutting a new release. What I really like about the CircleCI setup we have is that it makes it possible to release a new version by pushing a new tag, ie by just creating a new release in GitHub.
That's how I deploy all my OSS projects via GH Actions.
Well, right now CircleCI is broken for durable-queue so it's probably moot: https://app.circleci.com/pipelines/github/clj-commons/durable-queue/4/workflows/27dd276b-d15a-4dad-9794-1727de603c92/jobs/6
I've pushed a bunch of updates today to master. I've run the basic tests against Clojure 1.10 / 1.11 / 1.12 (not automated yet). I will probably set up GH Actions so I can do both matrix Java and matrix Clojure testing, and set it up like I have next.jdbc, HoneySQL, etc so a tag or release causes a Clojars deployment.
My projects actually push a SNAPSHOT on every master push BTW, which can be good for users.