Migration Guide

Use this page to plan safe upgrades between Diwa versions. The current release stream has no mandatory major migration path yet; this guide is ready for the first breaking release.

Current Status

As of March 18, 2026, there is no required major-version migration for Diwa consumers. Keep dependencies within the current major and monitor this page for migration checklists once the next major cycle starts.

Before You Upgrade

1. Read the changelog entry for the target version and note Added/Changed/Deprecated/Removed items.
2. Run component and accessibility test suites before upgrading to establish a baseline.
3. Upgrade in a branch and validate key user flows (forms, feedback, navigation) with keyboard-only testing.
4. Search for deprecated props/events and replace them before shipping.

Codemod and Manual Step Template

Use this template when a major migration publishes codemods. Replace file names and transforms with the version-specific migration package.

# 1) Install migration tooling (example)
npm install --save-dev jscodeshift

# 2) Run codemod (example placeholder)
npx jscodeshift -t codemods/diwa-vNext.ts src

  # 3) Run tests and build
  npm test
npm run build:storefront

If no codemod is available for a release, follow the manual rename and behavior checklist in that release-specific section.

Next Actions

Check Changelog View Roadmap Back to Developing Intro