Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: review and bump clj-watson deps #75

Closed
lread opened this issue Aug 1, 2024 · 0 comments · Fixed by #85
Closed

chore: review and bump clj-watson deps #75

lread opened this issue Aug 1, 2024 · 0 comments · Fixed by #85
Assignees

Comments

@lread
Copy link
Contributor

lread commented Aug 1, 2024

Some of clj-watson's deps have become stale.

Review each dep and bump to the current available release, if possible.

lread added a commit to lread/clj-watson that referenced this issue Aug 3, 2024
CI setup-clojure action
- moved action to current release instead of @master
- renamed deprecated `tools-deps` input to `cli`
- move to clojure version 'latest' (just like we do for each major JDK version)

CI
- report tools' versions to allow for reproducibility

clj-watson simple safe-looking bumps:
- clojure
- edamame
- cheshire
- clj-http
- tools.deps (has not changed much)
- selmer

clj-watson less safe-looking:
- org.apache.maven.resolver/maven-resolver-transport-http (deleted) -
this dep is automatically included by tools.deps, and clj-watson does
not reference it directly, and I don't see a rationale in git history
for why we need to override the transitive version. It might have been a
CVE or bug sometime in the past, let's see if we still actually need it.

Dev only:
- nrepl
- clojure-lsp-standalone
  - also suppressed unused public var for scan entrypoint
  - committed new .clj-kondo lib exports
- kaocha
- test-check (deleted, unused)
- state-flow (deleted, unused)
- mockfn (delete, unused)

Other deps.edn changes:
- delete `:mvn/repos` entry as it is no different from defaults

Closes clj-holmes#75
@lread lread mentioned this issue Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant