JHipster release v9.2.0
This is a minor release for JHipster v9.
It includes 515 closed issues and pull requests after the 9.1.0 release.
What's new?
- Our 3000+ EJS templates are now checked and formatted by eslint
- Upgraded to Spring Boot 4.0.7 and improved generated backend hardening with a safer AccountResource
- Made Vitest the only frontend test framework for generated apps with Jest removal from client choices and Angular cleanup of leftover Jest conditionals
- Included an application generation fix for initial project generation
- Fixed generated frontend behavior across Angular, React, and Vue with PUT support for entities without autogenerated IDs, a React entity creation fix, and a Vue Boolean field rendering fix
- Improved blueprint generation and internals with stronger generate-blueprint typing and compatibility, reworked bootstrap generator composition, and MemFsEditorFile integration
- Upgraded build tooling to Node 24.18.0, Gradle 9.6.1, and webpack-dev-server 6
Closed tickets and merged pull requests
As always, you can check all closed tickets and merged pull requests here.
How to install
To install JHipster v9.2.0 using NPM:
npm install -g [email protected]
It is also available using the JHipster Docker image, as it is automatically built from our source code.
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
You can also use the migrate blueprint for more advanced upgrade features.
npm i -g generator-jhipster-migrate
jhipster-migrate
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:
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 --single-entity
Help and bugs
If you find any issue with this release, don't hesitate to:
- Add a bug to our bug tracker
- Post a question on Stack Overflow
- Create a new discussion on GitHub
If the issue you have is an urgent bug or security issue, please:
- Contact @jhipster on Twitter