Skip to content

Migration Guide 3.16

Martin Kouba edited this page Sep 5, 2024 · 18 revisions
Table of Contents
Note

We highly recommend the use of quarkus update to update to a new version of Quarkus.

Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

WebSockets Next

When an error occurs but no error handler can handle the failure, Quarkus uses the strategy specified by the quarkus.websockets-next.server.unhandled-failure-strategy configuration property. The default values changed. For server endpoints, the error message is logged and the connection is closed. For client endpoints, the error message is logged. Previously, for both server and client endpoints the connection was closed silently by default.

Current version

Migration Guide 3.17

Next version in main

Migration Guide 3.18

Clone this wiki locally