Skip to main content

JHipster release v9.0.0-beta.2

The 9.0.0-beta.2 release is now available! This release includes 1,045 closed issues and pull requests from the community since 9.0.0-beta.0, with 1,036 associated with the 9.0.0-beta.1 milestone and 9 assigned to 9.0.0-beta.2.

The 9.0.0-beta.1 release included an issue that made it unusable. This 9.0.0-beta.2 release addresses that problem and contains all related fixes.

What's new?​

Spring Boot​

  • Spring Boot 4: Upgraded to Spring Boot 4.0.2 (#32035)
  • Migrated to EnableWebSocketSecurity (#31539)

Angular​

  • Angular 21: Updated to Angular v21 and dropped Jest support (#31458)
  • Converted more fields to signals (#31727, #31718)
  • Removed SharedModule/CommonModule in favor of standalone components (#31623, #31695)

Platform & Toolchain Updates​

  • Dropped Java 17 support: Java 21 is now the minimum required version (#31903)
  • Dropped Node 20 support: Node 22+ with native TypeScript support is now required (#31845)
  • Node.js upgraded to 24.12.0 (#31648)
  • Gradle upgraded to 9.3.1 (#32121)

Closed tickets and merged pull requests​

See the 9.0.0-beta.1 and 9.0.0-beta.2 release notes on GitHub for more details.

How to install​

To install JHipster v9.0.0-beta.2:

npm install -g [email protected]

It is also available using the JHipster Docker image, as it is automatically built from our source code.

How to upgrade​

Automatic upgrade

For an automatic upgrade, use the JHipster upgrade sub-generator on an existing application:

Upgrade your version of JHipster:

npm update -g generator-jhipster

And then run the upgrade sub-generator:

jhipster upgrade

You can also use the migrate blueprint for more advanced upgrade features.

npm i -g generator-jhipster-migrate
jhipster-migrate

Manual upgrades

For a manual upgrade, first upgrade your version of JHipster with:

npm update -g generator-jhipster

If you have an existing project, it will still use the JHipster version with which it was generated. To upgrade your project, you must first delete its node_modules folder and then run:

jhipster

You can also update your entities one-by-one by running again the entity sub-generator, for example if your entity is named Foo, use:

jhipster entity Foo --single-entity

Help and bugs​

If you find any issue with this release, don't hesitate to:

If the issue you have is an urgent bug or security issue, please: