live wire
▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸AI · vLLM Recipes maps Muse Spark Open to single-node Blackwell and AMD deployment (Oct. 16)vLLM▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security
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