News
JHipster 9.0.0-beta.2 lands with Spring Boot 4 upgrades and a clear message for Java teams: it's Java 21 time
- By John K. Waters
- February 3, 2026
The JHipster team has shipped JHipster 9.0.0-beta.2, a follow-up to the project's first 9.0 beta, aimed squarely at improving generator stability while pushing the stack forward with Spring Boot 4.x.
If you tried 9.0.0-beta.1 and hit rough edges, beta.2 is the release you actually want to evaluate. The team says beta.1 has been deprecated, and recommends upgrading to beta.2 to avoid the generator issues that surfaced in early testing.
What Java Developers Will Care About Most
Spring Boot 4 migration continues (now on 4.0.2)
JHipster 9 is the project's biggest Spring Boot jump in a while, and beta.2 moves the baseline to Spring Boot 4.0.2. For Java shops that standardize on Spring Boot starters and conventions, this is the "headline" change: it signals where JHipster's Spring ecosystem alignment is headed and what version family-generated apps will assume going forward.
WebSocket security: new approach, fewer deprecated hooks
Beta.2 also updates WebSocket security configuration by implementing @EnableWebSocketSecurity, replacing older patterns tied to deprecated Spring Security components. If your generated app uses STOMP/WebSocket messaging, this matters because it affects how security rules are applied and where you'll customize them.
Java 21 becomes the minimum requirement
JHipster 9 drops Java 17 support and makes Java 21 the new floor. For teams planning platform upgrades, this is the real gating factor: it changes CI images, dev workstation setups, and the compatibility matrix for frameworks and internal libraries.
Practically, it also nudges Java teams toward newer runtime capabilities (like virtual threads and newer language/runtime enhancements) while simplifying JHipster's own support burden around older toolchains.
The "Java-adjacent" changes you'll still trip over
Even if you're primarily a backend Java developer, JHipster-generated projects are full-stack by design—so 9.0 also updates the toolchain that wraps your Spring Boot app:
- Node.js: Node 20 is no longer supported; Node 22+ is now required.
- TypeScript: The release adds native TypeScript support (useful if your team is tightening type safety across the stack).
- Frontend defaults: Angular 21 is the updated target, and the testing framework shifts from Jest to Vitest.
- Testcontainers modernization: JHipster's integration tests migrate toward DynamicPropertySource usage across multiple backing services—SQL databases, MongoDB, Elasticsearch, Redis, Couchbase, and Kafka—to make containerized integration testing more consistent across environments.
The team also says they used the 9.0 cycle to overhaul parts of the project's CI and testing infrastructure, which should translate into more predictable generator output and fewer "works on my machine" surprises as the betas progress.
Where 9.0 stands right now
This is still a beta train. JHipster 9.0 remains in active development, and the project hasn't announced a general availability date yet. For Java teams, the best way to treat beta.2 is as a compatibility and migration preview: validate Java 21 readiness, confirm Spring Boot 4 behavior in your app patterns, and test any WebSocket security customizations early—before the final release locks in defaults.
If you already pulled beta.1, the guidance is simple: move to 9.0.0-beta.2 for stability fixes and the updated Spring Boot baseline.
About the Author
John K. Waters is the editor in chief of a number of Converge360.com sites, with a focus on high-end development, AI and future tech. He's been writing about cutting-edge technologies and culture of Silicon Valley for more than two decades, and he's written more than a dozen books. He also co-scripted the documentary film Silicon Valley: A 100 Year Renaissance, which aired on PBS. He can be reached at [email protected].