Skip to main content

JHipster release v8.7.2

This is a patch release for JHipster v8.

It includes 347 closed issues and pull requests on the main branch after the 8.7.1 release.

What's new?​

  • Upgrade to Spring Boot 3.3.5 (#27677)
  • Add support for Java 23 (#27345)
  • Don't generate Docker Compose configuration when no services are detected (#27437 and #27380)
  • Downgrade Sass to avoid warnings when running npm start with React and Vue (#27528)
  • Use Bootstrap v4 themes for Vue client (#27465)
  • Resolve Faker 9 breaking changes (#27368)
  • Upgrade to Angular 18.2.9 (#27661)
  • Upgrade to Vue 3.5.12 (#27568)
  • Upgrade to Node v20.18.0 (#27494)

Closed tickets and merged pull requests​

See the 8.7.2 release notes on GitHub for more details.

As always, you can view all closed tickets and merged pull requests.

How to install​

To install JHipster v8.7.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

Since JHipster 8.0, this command will update your project and all its entities.

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

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: