Migration Guide

Steps to migrate from HCM v1.7 to v1.8

HCM Upgrade Guide

1

Update Health Campaign Configurations

• Open the health-campaign-config repository.

• Merge the following PR changes into the appropriate branch: 🔗 HCM v1.8 Config Changes

• After merging, apply the Project Factory V2 API Persister changes: 🔗 Project-factory Persister Changes

2

Apply DevOps Changes

• Go to the health-campaign-devops repository.

• Check out the release-github-actions branch.

• Apply the following commits in order (very important):

  • Commit 1

  • Commit 2

  • Commit 3

  • Commit 4

• Add DevOps updates on top of the branch that holds the HCM v1.7 DevOps changes.

3

Update Seed Data & Localisation

• Seed Data Update

  • Use the updated seed data dump provided here: 🔗 Seed Data File

  • Import this dump into the environment. This will replace/upgrade the existing seed data with the updated version needed for HCM v1.8.

  • No manual picking of changes from the document is required.

• Localization Update

  • The reference document lists the updated translations/localization changes: 🔗 Reference Document

  • Use the finalized localization files (JSON/CSV) that are shared along with the migration package. These files should be applied directly to update the localization.

4

Update Project Builds

Update the build versions in dependency-chart-v1.8.yaml:

Service	New version
workbench-ui	v0.4.0-51d99a279e-514
project-factory	v0.4.0-ac42230ae7-576

5

Final Verification

• Ensure all the above changes are committed and pushed to the correct branches.

• Deploy the updated version in the new environment.

• Test the environment for:

  • Functionality changes from v1.8 configs.

  • Project Factory V2 API functionality.

  • Seed data correctness.

  • UI rendering in the workbench.

• If all tests pass, proceed to promote changes to the required environments.

APK Upgrade Guide

Below are the steps to upgrade from v1.7.0 → v0.2.0.

1

Upgrade app version

The app version has been bumped: version: 1.7.0 → version: 0.2.0

2

Update dependencies

The following packages were upgraded in pubspec.yaml:

Package	Old version	New version
digit_ui_components	^0.0.2-dev.14	^0.2.2+4
sync_service	^1.0.0	^1.0.2
attendance_management	^1.0.4+1	^1.0.5+1
digit_scanner	^1.0.5	^1.0.6+1
inventory_management	^1.0.5	^1.0.6
referral_reconciliation	^1.0.4	^1.0.6
digit_data_model	^1.0.6	^1.2.0-dev.1-console
registration_delivery	^1.0.6	^1.1.0-dev.5-console
digit_dss	^1.0.4	^1.0.4+2
closed_household	^1.0.5	^1.1.0-dev.1-console
survey_form	^1.0.1	^1.0.3
complaints	^1.0.2	^1.0.3

The following new packages were introduced in 1.8.0:

Package	Version
digit_crud_bloc	^0.0.2-dev
digit_data_converter	^0.0.2-dev
digit_forms_engine	^0.0.2-dev

3

Apply updates

Step 1 — Update dependencies

Run: flutter pub upgrade

👉 This updates all packages to the latest versions that match your pubspec.yaml.

Step 2 — Clean project (to avoid old cached versions)

flutter clean
flutter pub get

Step 3 — Verify updates

Run: flutter pub outdated

👉 This shows you if any dependencies are still behind the latest release.

Summary

• App version bumped: 1.7.0 → 0.2.0

To update locally:

• flutter pub upgrade

• flutter clean

• flutter pub get

• flutter pub outdated