Improve this page

JHipster release 4.5.5 Permalink to "JHipster release 4.5.5"

What’s new Permalink to "What’s new"

This is the fifth patch release for JHipster v4.5.0.

This release corrects a security issue in the JHipster Registry (see jhipster/jhipster-registry #150), and is a recommended upgrade for people using it.

Other noteworthy changes several updates in our Angular 4 code, as we move forward to release it out of beta - see #5907 #5926 #5932.

Closed tickets and merged pull requests Permalink to "Closed tickets and merged pull requests"

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

How to upgrade Permalink to "How to upgrade"

Automatic upgrade

WARNING we have many reports that automatic upgrade do not work well, see #5883. This depends on your specific configuration, 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:

yo jhipster:upgrade

Please note that with our new JHipster CLI release, the new command will be:

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 Permalink to "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: