national-social-registry
Published automatically.
Repository: github.com/OpenG2P/national-social-registry · Container images: Container Registry
| Version | Date | Type | Notes |
|---|---|---|---|
0.0.0-develop.242 |
2026-08-28 | develop |
Develop builds
national-social-registry — develop 0.0.0-develop.242 (2026-08-28)
commit 33a905d · changes since 1.1.0
Chart: openg2p-nsr 0.0.0-develop.242
Summary
- Major: Reporting enhancements: refreshed reporting views on a schedule with a new CronJob, added materialized views for vulnerability, livelihood, and housing data, and improved integration with the platform generator for additional reporting tables.
- Data integrity improvements: seeded real birth dates for packs instead of a default date, and fixed AWE seed conflicts to prevent batch failures due to policy key clashes.
- Cleanup and optimization: removed G2PRegisterDomainFactory and related files to streamline initialization, and eliminated the unreferenced import-dashboards-job.yaml.
- CI/build updates: reverted build and publish process to GitHub, and updated the RP version multiple times for ongoing development.
- Documentation and minor fixes: included minor documentation updates and corrections in helm comments, ensuring clarity and accuracy.
Changes
- G2P-5605 Build and publish on GitHub again (
33a905d) - Bumpd up RP version to 0.0.0-develop.392 (
966cf10) - Bumped up RP version to 0.0.0-develop.391 (
334a82d) - G2P-5554 Seed the pack's real birth date instead of inventing 1 January. The pack carried only a year, so every sample individual in the country shared a birthday; older packs still fall back, since a date column cannot hold a year. (
9b04d6c) - Minor doc update. (
c4b8cb8) - G2P-5524 Remove G2PRegisterDomainFactory and related files. The factory class and its dependencies have been eliminated to streamline the initialization process in the app. (
6019eb0) - Minor correction in helm comments. (
9169386) - Bumped up RP version to 0.0.0-develop.383 (
2fc8b9e) - G2P-4804 Bring the reporting layer to parity with the Farmer Registry. Materializes the vulnerability, livelihood and housing views — 259k, 166k and 62k rows, each joining a materialized parent on every read — inherits the individual's sex and age band onto its five child views so those questions need no join, and adds the devOverlay switch for testing the platform generator without publishing an image. (
69bc95f) - G2P-4804 Take the mechanical reporting views from the platform generator. reporting.yaml declares the entity tree and names household/individual as hand-written; the generator adds fourteen more, including the vulnerability and livelihood tables holding 259k and 166k rows that had no reporting view at all. (
fb74480) - G2P-4804 Refresh the reporting views on a schedule, instead of relying on Insights to do it. They are materialized, so they held whatever the install produced and every household registered afterwards was invisible with no error anywhere; a CronJob now rebuilds them in dependency order resolved from pg_depend, on analytics.reportingViews.refreshSchedule. (
9dbd065) - G2P-4804 Drop the inline maps <style>; the platform injects the shared theme at build time. (
623c313) - G2P-5378 Fix AWE seed aborting on shared-DB policy_key clash: untargeted ON CONFLICT DO NOTHING (uq_policy_key_version was unguarded by the id-targeted clause) plus FK-orphan filters on stages/rules, so a policy another registry already owns no longer takes the whole batch — and the farmer policy — down with it (
ffc0017) - G2P-4804 Fall back to this registry's own Superset connection name when the release is gone. The name was only ever read from
helm get values, so uninstalling from Rancher — or running helm uninstall first — skipped the dashboard cleanup with a quiet warning and left the dashboards, charts, datasets and connection in the shared Superset, where the next install adopted them by UUID. (9b5f4cf) - G2P-4804 Skip the dashboard import when Superset is absent instead of failing the install. Superset is a separate release and analytics is optional, but the gate exited 1 after waiting, so a registry installed without a reporting stack failed outright. The gate is checked in the init container AND the main one, because an init container exiting 0 does not stop the pod; set analytics.dashboards.superset.required=true where a silent skip would be worse. (
7815d1f) - G2P-4804 Point the maps page at the
registrysource. It still queried nsr.*, which stopped resolving when the Evidence source was renamed, so the page would not have built. (a1a513b) - G2P-XXXX Dashboards: drop the standalone import-dashboards-job.yaml — unreferenced, superseded by the chart's hook Job, and three fixes behind it (
5ccc675) - Moved to GitLab: openg2p/registry/national-social-registry (read-only; build/publish disabled) (
7b92133)
What's shown here. This catalogue lists every stable release, plus the latest 20 develop builds and the latest 10 release candidates per release line -- candidates are KEPT after their release ships, as the audit trail of the release run. Older develop builds and release candidates are pruned as they are superseded. Those versions still exist in the container and Helm registries — they are simply not listed here. This page is generated automatically from commit history; do not edit it by hand.
