live wire
▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache Camel▸AI · EAGLE-4 0.1.4 fixes multi-GPU vLLM collective ordering during startupEAGLE-4▸SECURITY: Apache Camel 4.23.0, 4.22.2 and 4.18.5 fix eight component vulnerabilitiesApache Camel▸AI · Red Hat shows DRA doubles llm-d KV-cache throughput by aligning GPUs and RDMA NICsRed Hat Developer▸Red Hat Developer Hub 1.9.10 ships as a Critical security updateRed Hat errata▸OpenShift Dev Spaces 3.31 adds live editor switching and DevWorkspace Operator 1.0Red Hat documentation▸OpenShift Pipelines 1.24.1 tightens Manual Approval Gate RBAC and approval integrityRed Hat release notes▸AI · Red Hat survey: 97% of UK CIOs trust agent security, but 43% can trace data flowsRed Hat▸JAVA · IBM and Kaggle launch a living benchmark for agentic Java framework migrationsIBM Research▸AI · Red Hat tests policy-derived data controls for AI agentsRed Hat▸Apache Camel pattern turns routes into bounded LLM tools and MCP servicesRed Hat Developer▸Atos tunes small models on OpenShift AI for structured German-language analysisRed Hat Developer▸Red Hat publishes checklist for evaluating third-party OpenShift applicationsRed Hat Developer▸SECURITY · OpenShift 4.21.40 patches OpenSSL, OpenSSH and PCRE2 flawsRed Hat Product Security▸SECURITY · Apache Camel fixes A2A webhook SSRF gap in 4.22.2 and 4.23.0 (Oct. 23)Apache 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