Chenile 2.1.29

Chenile 2.1.29 adds opt-in numeric JPA identifier support. It is a compatible release: existing String-ID ChenileEntity applications, existing ID generators, and STM/workflow persistence continue to work unchanged.

Deployment summary

Item	DevOps action
Framework version	Upgrade the Chenile parent and application modules together to 2.1.29.
Database migration	None is required by the framework.
Existing applications	No configuration or code change is needed when existing String identifiers are retained.
Rollback	Redeploy the prior framework version; no framework-owned schema/data change must be reversed.

Do not change a deployed entity’s primary-key type in place as part of this framework upgrade. Moving an existing table from String IDs to numeric IDs is an application data migration and must be planned, backfilled, and rolled out by the owning team.

Numeric JPA IDs

Applications that create new non-workflow JPA entities can now opt into framework base classes for database-generated Long or Integer identifiers, or use the new typed application-generated ID extension points. This avoids forcing String identifiers where a conventional numeric relational key is the right model.

This is deliberately additive:

• Existing entities extending ChenileEntity retain their String-ID behavior.
• Existing IDGenerator users retain their behavior.
• STM/workflow entities are not changed by this feature.
• A new application chooses the numeric base class and its usual JPA generator strategy; there is no global switch that converts existing entities.

For entity design examples and the available generated-ID bases, see Numeric JPA identifiers.

Promotion checks

1. Keep an existing String-ID entity test in the application suite.
2. For each new numeric entity, verify create, retrieve, update, and relationship mappings against the target database.
3. Confirm schema generation or the managed migration creates a numeric identity/sequence column that matches the selected JPA strategy.
4. Exercise any API serialization and client contracts that expose the new identifier type.

Meaningful Git changelog

Repository	Change	DevOps relevance
chenile-core	Add numeric JPA ID support	New opt-in entity bases and typed generator support; no action for String-ID applications.

The remaining 2.1.29 commits align module versions only. They are intentionally omitted from this meaningful changelog.

Upgrade path to 2.1.30

2.1.30 follows this release and adds workflow/query, process-management, and Azure messaging features. Read the 2.1.30 release notes before adopting any of those opt-in capabilities.