adobe/commerce-app-migration
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
9b6e61cThanks @obarcelonap! - Use Node.js 26 by default in action examples and migrations. -
#809
8513cc2Thanks @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
8513cc2Thanks @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
f124cf4Thanks @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
32988bbThanks @aminakhyat! - Note that credit memo view buttons are new v2-only registrations in the Admin UI SDK migration agent. -
#802
a03c546Thanks @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
8f28544Thanks @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
d78221eThanks @obarcelonap! - Guide migrated projects to use theinclude-ims-credentialsannotation andresolveImsAuthParamsinstead of manually wired IMS credential inputs.
1.3.2
Patch Changes
-
#627
e5cbdf1Thanks @obarcelonap! - Document the allowed values for Commerce webhook types and HTTP methods. -
#642
79dcda0Thanks @iivvaannxx! - Document automatic and manual desired-state upgrades in migrated app configuration and deployment guidance.
1.3.1
Patch Changes
-
#602
1dc6031Thanks @obarcelonap! - Publish this plugin's changelog history alongside its skills. -
#606
a18a250Thanks @iivvaannxx! - Remove obsolete pnpm esbuild build approval steps from Commerce app migrations.
1.3.0
Minor Changes
-
#593
554bc21Thanks @iivvaannxx! -commerce-app-migrategains aspectrum-s2-upgradereference so the migration executor can detect classic React Spectrum (v3) in a project's Admin UIweb-srcand offer to run the S1-to-S2 migration for the user. -
#594
a947231Thanks @iivvaannxx! - Improved thecommerce-app-migrateskill:initruns 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 forERR_PNPM_IGNORED_BUILDS. - Descriptions over 255 characters are rewritten into a coherent shorter summary instead of truncated mid-sentence.
- The original
package.jsondescription is restored ifinitwrites back the shortened config value. - The migration summary opens with a one-line TL;DR.
1.2.0
Minor Changes
- #540
6382582Thanks @obarcelonap! - Promote Commerce plugins through the stable skills release process.