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
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