JHipster release 3.6.1


This is a minor release, correcting a few bugs from yesterday’s 3.6.0 release.

  • Several primary keys have had their length reduced because of #3996. This caused a bug with older (4.6) versions of MySQL, but those length were too big, so it’s a good thing to reduce them if possible. If you have an existing database, you don’t have to alter your tables: having a bigger PK doesn’t do any harm, so migration is totally optional.
  • The Elasticsearch Docker image has been upgraded to v2.3.5, which is its latest version, and which works with Spring Boot 1.4. See #4000.
  • Kubernetes now uses the same image versions as Docker. See #4002.

Closed tickets

一如既往, you can check all closed tickets here.


For an automatic upgrade, starting with JHipster v3.4.0, use the JHipster upgrade sub-generator on an existing application:

yo jhipster:upgrade

选择手动升级, 需要先升级你的Jhipster版本:

npm update -g generator-jhipster

如果你已经有了一个项目, 将会继续使用当时项目生成的Jhipster版本. 如果需要升级你的项目, 你需要先删除node_modules文件夹再运行:

yo jhipster


yo jhipster --with-entities

你也可以使用实体类子生成器挨个更新你的实体类, 例如你的实体类名字是_Foo_

yo jhipster:entity Foo


如果您发现这个版本的任何问题, 请随时联系我们:

If the issue you have is an urgent bug or security issue, please: