Skip to content

downgrade ring-defaults to be compatible with ring version#329

Merged
daslu merged 1 commit into
scicloj:mainfrom
holyjak:patch-1
Feb 23, 2026
Merged

downgrade ring-defaults to be compatible with ring version#329
daslu merged 1 commit into
scicloj:mainfrom
holyjak:patch-1

Conversation

@holyjak

@holyjak holyjak commented Feb 20, 2026

Copy link
Copy Markdown
Member

Context:
ring/ring-defaults 0.7.0 is not compatible with the ring/ring 1.14.1 that Clay claims to depend on, because it uses the content-length middleware, which has only been added to ring in v. 1.15.0 (see https://github.com/ring-clojure/ring/blob/master/CHANGELOG.md#1150-beta1-2025-07-22).

Fix:
Downgrade ring-defaults back to 0.6.0, before it added the wrap-content-length middleware.

ring/ring-defaults 0.7.0 is not compatible with ring/ring1.14.1, because it uses the content-length middleware, which has only been added to ring in v. 1.15.0 (see https://github.com/ring-clojure/ring/blob/master/CHANGELOG.md#1150-beta1-2025-07-22)
@daslu

daslu commented Feb 23, 2026

Copy link
Copy Markdown
Member

Thanks, @holyjak!

@daslu daslu merged commit 5b95397 into scicloj:main Feb 23, 2026
@daslu

daslu commented Feb 26, 2026

Copy link
Copy Markdown
Member

@holyjak
I will deploy your fix today.

If I understand correctly, this is supposed to fix the problem you mentioned with Calva here:
BetterThanTomorrow/calva-power-tools#37 (comment)

However, trying Clay after your change does not seem to fix the current Calva behaviour (where the inline Clay view is simply empty).

I am wondering what else might be the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants