live wire
▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer
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