Update all dependencies to current versions#48
Merged
Conversation
All deps were 6+ years old. Also drops Clojure 1.7-1.9 support (minimum is now 1.10) and adds 1.11/1.12 to the test matrix. The nREPL 1.x upgrade required keywordizing JSON keys in the client transport, since nrepl.core/message now filters responses by keyword :id. Ring 1.15.3 pulls in Jetty 12 which needs Java 17+, so Java 11 is dropped from the CI matrix.
bbatsov
force-pushed
the
update-dependencies
branch
from
1bdf7c4 to
285acbc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All dependencies were 6+ years old (from 2018-2019). This brings everything up to date: nREPL 1.5.2, Ring 1.15.3, Cheshire 6.1.0, clj-http 3.13.1, Compojure 1.7.2, and lein-cljfmt 0.9.2.
Drops Clojure 1.7-1.9 support — minimum is now 1.10, tested against 1.10, 1.11, and 1.12.
The nREPL 1.x upgrade required a fix in the client transport:
json/parse-stringnow keywordizes keys, sincenrepl.core/messagefilters responses by keyword:id.