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
newsJAVA

Quarkus 4 enters beta and puts extension migration on the clock

The first Quarkus 4 beta raises the Java baseline, refreshes the networking and persistence stack, and asks extension maintainers to move before a planned late-November final release.

Quarkus 4 beta migration milestones leading to a late-November release.
Timeline: dates from the story
By The News Desk· Oct 10, 2026the quick take — two AI hosts go live when you do

Quarkus has published the first beta of its next major release, giving application and extension teams an early integration point for a stack-wide upgrade rather than another incremental 3.x update. Quarkus 4.0.0.Beta1 changes the baseline to Java 21 and introduces new major versions across the networking, persistence and serialization layers.

What changed

The beta moves Quarkus onto Netty 4.2 and Vert.x 5.x, with opt-in HTTP/3 support and automatic certificate generation for development and test modes. Native transport support extends to epoll and io_uring, including native executables.

The framework also adds an observation API for generating metrics and traces through Micrometer or OpenTelemetry, plus an out-of-the-box observability section in the development UI. The application stack advances to Jakarta REST 4, Hibernate ORM 8, Jakarta Persistence 4.0, Jakarta Data 1.1, Jackson 3 and CDI 5.0.

Messaging changes include a dedicated JMS extension with Spring JMS, pooled JMS and IronJacamar compatibility, alongside an @ExactlyOnce mechanism for Kafka transactions.

Who should care

Extension maintainers have the most immediate work. Quarkus says the migration guide is denser than its usual minor-release documentation and explicitly asks maintainers to begin porting now. Application teams should use the beta to expose compatibility breaks in dependencies and internal extensions while there is still time to report them upstream.

The Java 21 floor is also a planning boundary for teams carrying older runtime assumptions. Meanwhile, the combination of HTTP/3, QUIC-oriented networking, refreshed persistence APIs and Jackson 3 means testing should cover protocol behavior and serialization as well as compilation.

What to do

Quarkus plans the final release for the end of November. Teams evaluating the beta should first inventory extensions and confirm their Quarkus 4 status, then run representative integration tests against the new Java, networking, persistence and JSON layers. Extension authors should work through the project’s linked migration guide and report failures before the release candidate stage.

This is a beta, not a production recommendation. Its value is that it makes the migration surface concrete early enough for maintainers and platform teams to influence the final release instead of discovering incompatibilities after general availability.

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