live wire
▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache Camel▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache Camel
upstreambeat.ai
releaseJAVA

Quarkus 3.40 opens a new 12-month LTS line

The release carries the Quarkus 3.39 code line into a year of support and gives teams a documented path from the previous 3.33 LTS.

Old Quarkus LTS path versus new 3.40 LTS path.
AI-generated illustration
By The News Desk· Oct 1, 2026the quick take — two AI hosts go live when you do

Quarkus has released version 3.40 as its new long-term support line, giving application teams a 12-month support window for the release. The project says 3.40 is built on Quarkus 3.39 and is its direct continuation rather than a separate feature train.

What changed

The LTS designation is the main change. Quarkus says the core of 3.40 is based on 3.39, with additional fixes included in 3.40.1. For teams already running 3.39, the project says there is nothing extra to do when moving to 3.40 LTS.

The platform also updates a set of components around the framework. The release includes Camel Quarkus 3.40.0, Quarkus CXF 3.40.0, Quarkus LangChain4j 1.13.3, Quarkus MCP Server 2.0.1 and Debezium 3.6.3.Final. Other listed upgrades include Quarkus Amazon Services 3.22.1, Google Cloud Services 2.24.0, Operator SDK 7.8.0, Vault 4.10.0 and Qpid JMS 2.14.0.

Quarkus also said work is underway on the first beta of Quarkus 4. That work is separate from the new 3.40 LTS line announced here.

Who is affected

The release matters most to teams standardizing on supported Quarkus baselines. Users on the previous LTS, Quarkus 3.33, need to account for the changes introduced across versions 3.34 through 3.40. The announcement links the migration guide for each intervening release and notes that the 3.40 guide itself is empty because 3.40 continues 3.39.

Teams using the listed platform components should also check the new bundled versions as part of their upgrade review, particularly where application behavior or extension compatibility depends on those components.

What to do

Quarkus recommends installing the latest Quarkus CLI and running quarkus update. The project says the command can update applications from any Quarkus version, including 2.x, to 3.40 LTS.

That automation does not replace migration review. Quarkus says the update command should handle most of the heavy lifting, but some cases still require manual changes. Teams moving from 3.33 LTS should therefore work through the linked migration guides in sequence, test their extensions against the upgraded component set and verify application behavior before adopting 3.40 as their supported baseline.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk