What jhipster/generator-jhipster shipped

This week: pnpm support for applications and workspaces, a skipUserRegistration option, sign in on a page for Vue and React, and shared admin models behind the Angular, React and Vue screens.

This week in the generator: pnpm is now supported for applications and workspaces, with npm staying the default. A new skipUserRegistration option generates applications where only administrators create users. Vue and React sign in on a page instead of a modal. The Angular, React and Vue admin screens now render from shared client:spring-boot models for configuration, health and metrics. Spring Boot entities can be sorted by the columns of their to-one relationships, unknown sort paths answer with 400, and error responses follow the application format.

SQL Server apps can now deploy on Kubernetes and Knative. Knative apps stay registered in Consul with Istio, and Kubernetes Consul gossip traffic is encrypted. Liquibase uses the Hibernate 7 extension, and the jhipster run command accepts scoped namespaces.

This week's updates: SQL Server applications can now be deployed on Kubernetes and Knative, with database environment variables and storage configured. Knative applications using Istio now stay registered in Consul at the cluster address on port 80, and the Knative Helm apply script works with Helm 4. Kubernetes Consul servers now encrypt their gossip traffic with a valid, project-specific key. The Maven Liquibase plugin now uses the Hibernate 7 extension to match generated applications, and the helm and knative prerequisite checks no longer rely on a shell pipeline. The jhipster run command now accepts scoped namespaces, and the Vue client loads the account only on the first navigation.

This week: delayed entity defaults in base-application, entity changes computed once with a primary key warning, scoped blueprints in the JDL, jhipster under another package name, an interactive generate-sample, and a docker app healthcheck command.

This week in the repository: finalizeDefault and finalizeDefaultOrUndefined in generator-jhipster/utils, required relationships and their cycles as delayed entity defaults in base-application, and entity changes computed once with a warning when the primary key changes. The JDL accepts scoped blueprints in lists and namespace configs, and any application type checked by pattern only; the jdl API exports the importer, parse and getCst again. jhipster now runs installed under another package name, generate-sample asks for the workflow and sample when none is given, and the ci module exports the synchronous sample group readers. Docker gains dockerApplicationHealthcheckCommand, and the Elasticsearch health check waits for a yellow cluster.

This week: a server:i18n generator for server messages, a reproducible-secrets option for spring-boot, jdl definitions in runs without the cli, and fixes for entity git commits, blob fields and root package.json scripts.

This week in the generator: a new server:i18n generator that writes the server messages and per-language files; a reproducible-secrets option for the spring-boot generator that derives secrets and the development KeyStore from the creation timestamp; jdl definitions now available to runs without the cli; and the jdl generator merges over configuration written before from the in-memory file system. Fixes this week include committing generated entities to the existing git repository, converting every blob field stored as byte[], adding concurrently and wait-on to the root package.json of every application, and declaring reproducibleSecrets with the base options so blueprints can use it.

Couchbase is now on par with the other databases. Entity, field and relationship preparing tasks get defaults helpers, commands declare field types, validations and entity options, and the KeyStore is generated without keytool. Blueprint generators can be described in one call.

This week in the project: Couchbase is brought on par with the other databases, with relationships stored and read back like MongoDB and SQL and listings and searches checking their sort. The entities, fields and relationships preparing tasks receive defaults helpers, and commands now declare field types, validations and entity options, with JDL definitions and entity types derived from them. The spring-boot generator builds the KeyStore in memory without keytool, so no JDK is needed at generation time. Generators of JHipster and of blueprints are resolved through a GeneratorsResolver, letting tools describe blueprints with one call, and cli information about blueprint commands now goes to stderr.

Shipped this week: JDL workspace builder fixes, Elasticsearch transaction safety, CLI stability improvements, and better Angular signals support.

Week 36 focused on improving multi-application JDL support with proper environment building and stack configuration. Fixed critical issues with Elasticsearch indexing in reactive apps and JWT authentication. CLI build failures resolved. Framework improvements across Angular (signals), React (useEffect), and Vue continue the modernization efforts.

JDL parser now returns all diagnostics with source locations instead of throwing. External tools can access JDL definitions and runtime. React validation patterns with quotes work correctly.

This week's JDL parser improvements focus on better error reporting and tooling support. The parser now captures source locations for all AST nodes, reports diagnostics without throwing, and exports APIs for external tools like linters and editors. Meanwhile, deprecated dependencies in Java and JavaScript tooling were updated, and a React template generation bug with validation patterns containing quotes was fixed.

This week: Elasticsearch custom index names, Kubernetes refactoring, SQL Server 2025 support, improved ESLint rules, and JDL string literal escaping. Configuration consolidation improves maintainability.

JHipster's weekly update includes significant infrastructure improvements: Elasticsearch now supports custom index and field names for compatibility, Kubernetes generators refactored for cleaner composition, SQL Server container upgraded to 2025, and new ESLint rules enforce correct task execution order. JDL string literals gain escape support. Multiple refactoring PRs consolidate configuration definitions into command files for easier maintenance.