Skip to main content

JHipster release v8.7.3

This is a patch release for JHipster v8.

It includes 35 closed issues and pull requests on the main branch after the 8.7.2 release.

What's new?​

  • Fix testing support for blueprints (#27710)
  • Upgrade to Node 22 (#27722)
  • Fix no database daily builds (#27724)
  • Upgrade typescript-eslint from 8.11.0 to 8.12.1 (#27721)

Updated Blueprints​

note

The .NET Core and Node blueprints need modularization adjustments to work with JHipster 8.7.3 and therefore could not be updated.

Closed tickets and merged pull requests​

See the 8.7.3 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.3:

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 --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: