JHipster release v5.7.0 Permalink to "JHipster release v5.7.0"

This new minor release comes with 55 closed tickets and pull requests. It has 2 major improvements:

  • JHipster now uses UTC timestamps everywhere thanks to #8284. This follows our goal of generating full-stack, high quality applications. This will cause a few issues in existing applications, as we now force UTC (for example in the Hibernate configuration and in the Liquibase scripts), but the migration should be easy as this doesn’t touch a lot of lines of code.
  • The JDL has been refined, firstly by fixing several bugs (including in #8547), and secondly by adding support for deploying applications straight from the JDL. Depoyments only work with Docker-based tools for the moment, so we support Docker Compose, Kubernetes, Openshift and Rancher Compose. If you want more information the documentation is already updated in the JDL documentation.

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

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

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:


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: