Update http4s-core, http4s-dsl, ... to 0.23.36

[softwaremill-ci]

About this PR

📦 Updates

• org.http4s:http4s-core
• org.http4s:http4s-dsl
• org.http4s:http4s-server

from 0.23.34 to 0.23.35

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.http4s" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.http4s" }
}]

^{labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:1}

[adamw]

0.23.35 accidentally broke binary compatibility in http4s-core (WebSocketFrameDefragmenter.defragFragment lost its no-arg overload — restored upstream in http4s/http4s@964e1a36, released as 0.23.36). Since blaze-server 0.23.17 pulls in an older http4s-server whose WebSocketBuilder2.build calls the removed method, the client test server crashed at runtime with NoSuchMethodError, failing all client test suites.

Pushed a commit that bumps this PR to 0.23.36 and pins http4s-server to Versions.http4s in clientTestServer, so the server/core bytecode mix can't reappear when core is bumped ahead of the independently-versioned blaze. Verified locally: test server starts on http4s 0.23.36 + blaze 0.23.17 and /ws/echo round-trips correctly.

🤖 Generated with Claude Code