JHipster release 4.5.5
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.
Closed tickets and merged pull requests
How to 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:
Please note that with our new JHipster CLI release, the new command will be:
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:
You can also update your project and all its entities by running
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:
- Contact @jhipster on Twitter