UpgradeAll
UpgradeAll copied to clipboard
fix(deps): update ktor monorepo to v3.3.3
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| io.ktor:ktor-client-cio | 3.3.2 -> 3.3.3 |
||
| io.ktor:ktor-client-core | 3.3.2 -> 3.3.3 |
[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
ktorio/ktor (io.ktor:ktor-client-cio)
v3.3.3
Published 26 November 2025
Improvements
- KTOR-6837 Discrepancies when parsing URL host with CIO and Darwin engines compared to the rest engines
- KTOR-9050 Logging: SimpleLogger should be an object, not a class
- KTOR-9094 Jetty Client: Support HTTP/2 over cleartext (h2c)
- KTOR-9120 OpenAPI gen: missing operationId for KDoc fields
- KTOR-3019 Improve logging for CORS plugin
Bugfixes
- KTOR-8671 Netty: RejectedExecutionException during shutdown on MacOS when dev mode is enabled
- KTOR-9096 Darwin: New SSE handlers stop responding after canceling few SSE sessions
- KTOR-9125 Double ResponseSent invocation when exception is thrown after respond
- KTOR-8878 OpenAPI: StackOverflowError when a response object has property with @Contextual serializer
- KTOR-8947 Java, ContentEncoding: IllegalHeaderNameException is thrown for ":status" pseudo header with HTTP/2
- KTOR-9092 NettyHttp2Handler throws IllegalArgumentException: 'ktor.ApplicationCall' is already in use
- KTOR-8924 Curl: Client sends both Transfer-Encoding and Content-Length headers for DELETE requests with body
- KTOR-8838 Exception handling issue in client cache
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.