Registry Release Notes - v4.0.0
Version
4.0.0
Helm Chart Version
Release Date
17-Apr-2026
Description
First release of Registry Gen 2 - the domain agnostic registry platform
4.0.0 manifests the Farmer Registry (with the farmer domain models defined in the extensions repository)
Previous Version
—
Summary
OpenG2P Registry v4.0.0 implements domain agnosticism as the core architectural principle. The platform ships with a Farmer Registry as the first domain manifestation, built entirely using the extension framework without modifying core platform code. This release also includes performance optimizations, expanded authentication capabilities, enhanced data validation, and refined user management workflows.

Key features
Domain Agnosticism & Extensibility
Core registry is domain-neutral; domain-specific registries are implemented as extensions
Farmer Registry Manifestation
Reference domain implementation demonstrating extension architecture
Functional ID Generation
Decoupled ID generation via OpenG2P ID Generator; configurable per Register
Multi-Provider Authentication
OIDC/OAuth integration via OpenG2P IAM Service; ships with Keycloak support
Change Request Infrastructure
All write operations flow through centralized change requests with verification and approval
Version History
Every register change is logged as a version snapshot linked to its originating change request
Async Task Processing
Celery Workers and Beat for background ingestion, outgestion, deduplication, and computation
Encryption at Rest
Envelope encryption (AES + KMS) for sensitive fields
Audit & Verification Logging
Comprehensive verification logging with audit trails and user action attribution
For the complete feature list, see Features.
Components & versions
Refer to Helm Chart for details on components, dependent services and compability.
Component architecture
For detailed component architecture and repository descriptions, see Organization of Codebase.
Breaking changes
This is the first release of the Gen 2 Registry platform. This is complete new architecture and is NOT COMPATIBLE with Gen1 Registry (3.x and before).
Non Functional Requirements
Refer to Security and Performance Testing - Design & Approach Document
Interoperability Standards
The Farmer Registry implements the Farmer DCI Standards in the Ingestion and Outgestion pipelines.
Known issues
Refer to issue Jiras.
Testing
Deployment
For deployment of Registry, see Deployment.
Roadmap
For features planned for upcoming releases, see Versions.
Last updated
Was this helpful?