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
releaseINTEGRATION

Camel Quarkus 3.40.0 LTS lands as the project prepares for Quarkus 4

The integration runtime aligns with Camel 4.22.1 and Quarkus 3.40.1, while the project identifies 3.40 as the final feature line on Quarkus 3.

Camel Quarkus 3.40.0 LTS alongside Quarkus 3 moving toward 4.
AI-generated illustration
By The News Desk· Oct 1, 2026the quick take — two AI hosts go live when you do

Apache Camel has released Camel Quarkus 3.40.0 as a long-term support line, aligning the integration stack with Camel 4.22.1 LTS and Quarkus 3.40.1 LTS. The release supports Java 17 and Java 21.

That alignment matters more than the version-number synchronization alone. The project says Quarkus 3.40 is the final feature release in the Quarkus 3.x stream, with Quarkus development shifting to 4.x. Camel Quarkus will follow in a future 4.x release stream, after required work in both Camel core and Camel Quarkus.

What changed in 3.40.0

The published release notes list work across AI integration, observability, native compilation, transport security and build hygiene. For LangChain4j users, the release adds a dedicated support extension for Quarkus LangChain4j build-time integration, expands embedding-store integration testing and adjusts ingestion metadata and document-ID handling. It also fixes Weaviate native compilation and embedding-store auto-detection behavior.

On observability, the release adds traceCustomIdOnly configuration for both Micrometer Observability and OpenTelemetry 2. The issue list also includes TLS registry handling for configured protocols and cipher suites, origin-restriction documentation for Vert.x WebSocket consumers, and fixes affecting native-image behavior.

The release artifacts include source archives plus CycloneDX SBOMs in XML and JSON formats, each accompanied by signatures and SHA-512 checksums.

The planning signal

For application teams, 3.40.0 is the stable Quarkus 3-based Camel line to evaluate while the upstream projects begin the Quarkus 4 transition. The announcement does not give a delivery date for Camel Quarkus 4.x and explicitly says work remains in both Camel core and Camel Quarkus.

That makes this release a boundary rather than merely another feature train: teams can adopt the new LTS stack on Java 17 or 21 now, while treating Quarkus 4 compatibility as future work rather than an immediate migration requirement.

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