Skip to main content

JHipster release 4.8.1

What's new​

This is a patch release, which uses JHipster Registry 3.1.2, which was just released to correct a small configuration issue for people using the JHipster Registry in prod mode, using Git - see JHipster Registry #179. If you are not in this case, you don't need to upgrade!

If you are using AngularJS 1, we also changed the required NodeJS version. Please note that we still recommend to use an LTS version, as the "stable" version has an history of breaking up JHipster!

Closed tickets and merged pull requests​

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

How to upgrade​

Automatic upgrade

WARNING this has been fixed recently, so if you have trouble with this:

  • You can still do a "manual upgrade" (see below)
  • If you find anything helpful for us, please send us comments on ticket #5883
  • If you have time and want to help, don't hesitate to contribute on this part!

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

Upgrade your version of JHipster:

yarn global upgrade generator-jhipster

And then run the upgrade sub-generator:

jhipster upgrade

Manual upgrades

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

yarn global upgrade 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 project and all its entities by running

jhipster --with-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

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: