DocumentationLLM Apps

Upgrade an existing app upgrade-existing-app

Last update: October 23, 2026
IMPORTANT
Adobe LLM Apps is currently in Beta.
Features, workflows, and UI shown here do not necessarily represent the final state of the product. To join the Beta, send an email to llm-apps-beta@adobe.com.

Use this guide only if your app uses @adobe/llm-apps-runtime earlier than 1.2.0 or its EDS widgets use the LLM Apps SDK earlier than 0.1.13. Apps that already meet both requirements can proceed directly to Set up Adobe Analytics and Customer Journey Analytics.

In this guide: Learn how to update and verify an older app’s runtime and EDS SDK. Then return to the analytics setup guide to enable Analytics and verify collection.

Before you begin before-you-begin

You need access to the handler repository and, for apps with EDS widgets, the EDS repository linked to your app. If your app uses Adobe managed infrastructure, request code access before making updates. See Use Adobe managed infrastructure.

Creating another app is not required. Update only the components that are below the supported versions. You can reuse existing Adobe configuration that meets the analytics setup requirements.

For apps with EDS widgets, publish and verify the SDK update first, then merge the runtime update and redeploy the app. The two repository updates can be prepared independently, but both must be available before you test the analytics-enabled deployment.

Check and update the LLM Apps Action Repository upgrade-runtime

  1. Open the handler repository linked to your app and install its dependencies:

    code language-bash 
    npm install

  2. Check the installed runtime:

    code language-bash 
    npm ls @adobe/llm-apps-runtime

  3. If the runtime is earlier than 1.2.0, install the current version:

    code language-bash 
    npm install @adobe/llm-apps-runtime@latest
npm ls @adobe/llm-apps-runtime

    Confirm that the installed version is 1.2.0 or later. Keep a later supported version if your app already uses one.

  4. Confirm that the runtime dependency and its resolved version meet the minimum requirement. The application’s own version is separate from the runtime dependency.

  5. Run the repository’s checks. For the LLM Apps boilerplate:

    code language-bash 
    npm test -- --runInBand
npm run build
npm run lint

    Investigate failures before deploying. If a check already fails on the original version, record that baseline separately from any failures introduced by the upgrade. A successful local build does not verify analytics collection.

  6. Commit the dependency update and its lockfile, then push and merge the update into the handler repository’s default branch, usually main. Deployment clones that branch. An update that exists only locally or on an unmerged feature branch is not included in the deployment.

    When a lockfile exists, deployment installs dependencies with npm ci, which uses the recorded versions. Redeploying does not upgrade the runtime automatically. Before redeploying, confirm the upgraded dependency and resolved version on the default branch in GitHub.

Check and update the LLM Apps Widget Repository upgrade-sdk

For apps with EDS widgets, check the SDK in the EDS repository as well as the server runtime. Updating one repository does not update the other.

Some EDS repositories include copied SDK scripts without an npm dependency. The browser loads those served scripts directly, so the absence of a package entry does not mean the SDK is missing. Refresh the copied SDK distribution using your project’s SDK update process. Adding a persistent npm dependency is not required for a project that maintains the SDK as copied scripts.

For projects that manage the SDK through npm:

  1. From the EDS repository root, install the current SDK and confirm its version:

    code language-bash 
    npm install --save-dev @adobe/llmapps-sdk@latest
npm ls @adobe/llmapps-sdk

    Use 0.1.13 or later. Keep a later supported version if your project already uses one.

  2. Verify that installation refreshed the served SDK distribution. The installation hook overwrites the copied SDK scripts, so review any local customizations before committing. Updating only the dependency declaration does not update the scripts that EDS serves. See Install the LLM Apps SDK.

  3. Run the EDS repository’s checks, such as npm run lint, and check that an existing widget still renders and responds to interactions.

  4. Commit the refreshed SDK distribution together with any dependency and lockfile updates. EDS serves the copied scripts, not the installed npm package directly.

After either update method, push and merge the update into the EDS branch used by the action’s Script URL. Verify that the URL serves the updated SDK and that its supporting libraries load successfully. If the URL uses your EDS live site, complete the publication steps for that site.

Next step next-step

Return to Set up Adobe Analytics and Customer Journey Analytics. All apps must enable Analytics and deploy to collect events; upgrading the runtime or SDK alone does not enable collection.

After saving the Analytics settings, deploy to Stage and verify new action-call and widget-interaction events before deploying to Production. Confirm that the action and widget still work and that a single link selection produces one widget-interaction event.

Analytics starts collecting new interactions after the analytics-enabled deployment. The upgrade does not reconstruct interactions that occurred before collection was enabled.

recommendation-more-help
llm-apps-help-main-toc