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

Apache Camel 4.23 opens a new LTS line with Java 25 support

The integration framework’s new long-term-support release spans Java 17, 21 and 25 while landing a broad set of runtime, DSL and connector fixes.

Apache Camel 4.23 LTS compared with the prior baseline and Java 17, 21, 25 support.
Side by side: what changed
By The Release Desk· Oct 15, 2026the quick take — two AI hosts go live when you do

Apache Camel 4.23.0 is now the project’s new long-term-support release, giving integration teams a fresh baseline that supports Java 17, 21 and 25. The release announcement says the release contains 1,034 features and improvements, while the full release notes enumerate the fixes and artifacts.

What changed

The LTS designation is the consequential part of this release. Camel’s release notes identify 4.23.0 as the new LTS line and list Java 17, Java 21 and Java 25 as supported runtimes. The project published Maven BOM coordinates for both Camel core and Camel Spring Boot, plus signed source archives and CycloneDX SBOMs in XML and JSON formats.

The resolved-issue list is broad rather than centered on one flagship feature. It includes fixes for duplicate or lost work in storage and database consumers, graceful shutdown behavior, YAML route serialization and validation, Camel JBang development workflows, secret refresh, OAuth2 handling, MCP control operations and several connector-specific concurrency problems.

Who it affects

Teams choosing a maintained upstream baseline for new Camel deployments now have a new LTS option. The Java 25 support boundary also matters to platform teams planning runtime standardization, while users of Camel JBang, YAML DSL, cloud-storage consumers and transactional routes have concrete fixes to assess.

This is an upstream Apache Camel release. Users of vendor-packaged Camel distributions should verify the version and support policy of their distribution rather than treating the upstream artifact as an in-place vendor update.

What to do

Review the 4.23.0 resolved-issue list against the components and runtimes in use. For a new deployment, pin the published 4.23.0 BOM and verify on the intended Java version. For an existing deployment, test route serialization, consumer retry behavior, shutdown handling and connector-specific changes before moving the LTS baseline.

sources

Filed by The Release 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