Coming soon ChenAIle — agentic microservices: agents, AI tool calls, machine learning and a metrics-driven rules engine Learn more →

Release notes

Chenile’s repositories are versioned together under chenile-parent and released on one train, so a single version number moves the whole framework forward. The current framework version is v2.1.36 (also shown in the footer). Some releases may be work-in-progress and not yet on Maven Central.

By version

  • 2.1.36 — (in development) JGen and stm-cli move to their own release cadence (JGen 2.5.1, stm-cli 1.0.0; see JGen releases), and the stm-cli command leaves workflow-utils.
  • 2.1.35 — (tagged October 27; JGen released October 31) per-request service selection (serviceSelector), typed process work listeners, interceptor names checked at startup, a Quartz cron builder in the process console, and for JGen one validator for blueprint inputs, generation records and jgen -r, blueprints from GitHub, and Homebrew/JBang installs.
  • 2.1.29–2.1.34 complete history — consolidated feature and upgrade notes across the release train.
  • 2.1.34 — (tagged; parent published; dependent bundles validated) the chenile-process-worker-set blueprint, a shared concrete worker service, Kafka retry and dead-lettering for worker failures, and header-scoped queue publication.
  • 2.1.33 — (built and tested; publication pending) shared outbox and split crontab dependency management, server/worker process blueprints, composable generation and declarative input validation.

  • 2.1.31 — (release prepared; parent published, dependent artifacts pending) transport-neutral services, service-registry controls, durable process commands, trigger history, the React management dashboard, and multi-level JGen process blueprints.
  • 2.1.30 — numeric JPA id support; release-train alignment.
  • 2.1.29 — release alignment across the 11 repositories and documentation refresh.

For the complete, authoritative history — every tag and its diff, including 2.1.17–2.1.28 — see the GitHub releases:

How the version is maintained
The version shown across the site comes from one place (maven_version in _config.yml). A scheduled job bumps it forward to the newest published chenile-parent on Maven Central, and never downgrades — so a hand-set, work-in-progress version stays put until the release actually ships.