Given the massive community investment in developing all sorts of
tooling on top of nREPL, nREPL’s team pledges to evolve the project only in
a responsible manner and backwards-compatible ways.
It’s extremely unlikely that we’re going to break compatibility on the
protocol level ever (with the rare cases of changing/removing things
that existed, but we knew for a fact weren’t used). Most often
backwards compatibility would be broken on the implementation level
(usually it’s just removal of deprecated functionality).
That would always happen with plenty of lead time and would be annotated
accordingly in the changelog.
Features/APIs marked as "Experimental" are subject to changes.
Be mindful of those.