> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/release-notes/migration-guide.md). # Migration Guide Steps to migrate from HCM v2.0 to v2.1 ## HCM Upgrade Guide {% stepper %} {% step %} ### Latest Health Campaign Configurations * Open the health-campaign-config repository. * Check out the DEMO branch. * latest HCM-v2.1 release configs changes\ 🔗 [HCM v2.1 Config Changes](https://github.com/egovernments/health-campaign-config/tree/DEMO) {% endstep %} {% step %} ### Latest DevOps Changes * Go to the health-campaign-devops repository. * Check out the release-github-actions branch. * latest HCM-v2.1 release devops changes 🔗[HCM-v2.1 release devops changes](https://github.com/egovernments/health-campaign-devops/tree/release-githubactions) {% endstep %} {% step %} ### Update Seed Data & Localisation * **Seed Data Update** * Use the updated seed data dump provided here:\ 🔗[ Seed Data File](/health/deploy/installation/setup-project-data.md#load-project-data) * Import this dump into the environment. This will **replace/upgrade the existing seed data** with the updated version needed for HCM v2.1. * No manual picking of changes from the document is required. * **Localization Update** * The reference document lists the updated translations/localization changes:\ 🔗 [Reference Document](/health/deploy/installation/setup-project-data.md#load-localisation) * 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. {% endstep %} {% step %} ### Latest Project Builds all the latest build for HCM-v2.0 release 🔗 [HCM-v2.1 latest builds](https://github.com/egovernments/health-campaign-devops/blob/release-githubactions/config-as-code/product-release-charts/Health/dependancy_chart-health-demo-v2.1.yaml) {% endstep %} {% endstepper %} ## APK Upgrade Guide Below are the steps to upgrade from v2.0 → v2.1. {% stepper %} {% step %} ### Upgrade app version The app version has been bumped: version: 2.0. → version: 2.1 {% endstep %} {% step %} ### How to Apply These Updates #### Step 1 — Update dependencies Run: ``` flutter pub upgrade ``` {% hint style="info" %} 👉 This updates all packages to the latest versions that match your [pubspec.yam](https://github.com/egovernments/health-campaign-field-worker-app/blob/master/apps/health_campaign_field_worker_app/pubspec.yaml)l. {% endhint %} #### Step 2 — Clean project (to avoid old cached versions) ``` flutter clean flutter pub get ``` #### Step 3 — Verify updates Run: ``` flutter pub outdated ``` {% endstep %} {% step %} ### Package Version Bumps | Package | Old version (2.0.0) | New version (2.1.0) | | ------------------------ | ------------------- | ------------------- | | digit\_ui\_components | ^0.3.0 | ^0.3.2 | | sync\_service | ^1.0.3 | ^1.0.6 | | attendance\_management | ^1.0.6 | ^1.0.6+2 | | digit\_scanner | ^1.0.7 | ^1.1.0 | | digit\_data\_model | ^1.3.0 | ^1.5.1 | | digit\_dss | ^1.0.5 | ^1.0.5+2 | | survey\_form | ^1.0.4 | ^1.0.5 | | digit\_flow\_builder | ^1.0.0 | ^0.2.1 | | digit\_showcase | ^1.0.2+1 | ^1.0.3+1 | | digit\_location\_tracker | ^1.0.0 | ^1.0.0+1 | | digit\_formula\_parser | ^1.2.0 | ^1.2.1 | | transit\_post | ^1.0.0 | ^1.0.2 | ### New Packages Introduced in 2.1.0 | Package | Version | | ------------------------- | ------- | | digit\_face\_verification | ^0.0.2 | | digit\_crud\_bloc | ^0.1.1 | | digit\_data\_converter | ^0.0.4 | | digit\_forms\_engine | ^0.1.2 | | {% endstep %} | | | {% endstepper %} | | {% hint style="info" %} **Notes** * Verify the `digit_flow_builder` version — the 2.0.0 migration guide lists `^1.0.0`, but the local package `pubspec.yaml` is `0.2.1`. If the 2.0.0 entry was a typo, drop `digit_flow_builder` from the bump table and list it under **New Packages** instead. * `digit_crud_bloc`, `digit_data_converter`, and `digit_forms_engine` were renamed/repackaged from earlier internal packages (e.g. `global_bloc`) during 2.1.0 dev. Depending on release-note framing, they can be described as "renamed" rather than brand-new. * Versions above come from each package's own `pubspec.yaml`. The app's `apps/health_campaign_field_worker_app/pubspec.yaml` still pins some older constraints (e.g. `digit_data_model: ^1.5.0`, `survey_form: ^1.0.3`) — bump those before publishing. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/health/release-notes/migration-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.