Skip to content

adobe/commerce-app-migration

v1.4.0

Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach.

@adobe/aio-commerce-plugin-app-migration

1.4.0

Minor Changes

  • #770 9b6e61c Thanks @obarcelonap! - Use Node.js 26 by default in action examples and migrations.

  • #809 8513cc2 Thanks @obarcelonap! - Suggest moving environment variables that runtime actions still read to Business Configurations during migration, and rewrite the action code to read them from the app configuration.

Patch Changes

  • #809 8513cc2 Thanks @obarcelonap! - Stop treating the Commerce base URL environment variables as required after migration, and explain that the base URL now comes from associating the app in App Management.

  • #732 f124cf4 Thanks @asalloum5! - Clarify in the Admin UI migration guidance that invoice view buttons are new V2 registrations and must not be inferred from legacy order buttons.

  • #776 32988bb Thanks @aminakhyat! - Note that credit memo view buttons are new v2-only registrations in the Admin UI SDK migration agent.

  • #802 a03c546 Thanks @aminakhyat! - Note that return (RMA) view buttons are new v2-only registrations in the Admin UI SDK migration agent.

1.3.3

Patch Changes

  • #744 8f28544 Thanks @iivvaannxx! - Install, upgrade and uninstall now plan the operation and validate the plan before anything changes. Uninstalling removes what the app installed and what it can prove it owns, even without an installation record, and runs the uninstall of every custom installation step that ran and is still configured. Every lifecycle operation uses the Commerce instance stored at association.

  • #712 d78221e Thanks @obarcelonap! - Guide migrated projects to use the include-ims-credentials annotation and resolveImsAuthParams instead of manually wired IMS credential inputs.

1.3.2

Patch Changes

  • #627 e5cbdf1 Thanks @obarcelonap! - Document the allowed values for Commerce webhook types and HTTP methods.

  • #642 79dcda0 Thanks @iivvaannxx! - Document automatic and manual desired-state upgrades in migrated app configuration and deployment guidance.

1.3.1

Patch Changes

1.3.0

Minor Changes

  • #593 554bc21 Thanks @iivvaannxx! - commerce-app-migrate gains a spectrum-s2-upgrade reference so the migration executor can detect classic React Spectrum (v3) in a project's Admin UI web-src and offer to run the S1-to-S2 migration for the user.

  • #594 a947231 Thanks @iivvaannxx! - Improved the commerce-app-migrate skill:

    • init runs with the scoped package name (npx --yes @adobe/aio-commerce-lib-app@latest init) so first runs work without the library installed.
    • pnpm projects get esbuild's build script approved (onlyBuiltDependencies) before init, with recovery guidance for ERR_PNPM_IGNORED_BUILDS.
    • Descriptions over 255 characters are rewritten into a coherent shorter summary instead of truncated mid-sentence.
    • The original package.json description is restored if init writes back the shortened config value.
    • The migration summary opens with a one-line TL;DR.

1.2.0

Minor Changes