Upgrading

Preserve the app’s existing package manager and lockfile style.

Before Upgrading

Read release notes or package metadata before changing versions:

Then check the package’s release notes, changelog, GitHub releases, or npm package page for breaking changes, new features, migration notes, and peer dependency changes. If release notes are not available, inspect the version history and package metadata before choosing a target version.

Inspect the current app:

If the app does not use npm, run the equivalent package-manager commands.

Upgrade

For npm projects:

After upgrading, check and preserve:

• vite.config.ts Datadog plugin configuration, especially auth.site.
• package.json scripts such as dev, build, and upload.
• Existing backend function imports from @datadog/action-catalog/....
• Project-local instructions in AGENTS.md.

Compare Against A Fresh Scaffold

If the user asks for a feature that may come from the latest scaffolder, create a temporary baseline app and compare it with the existing project instead of guessing.

Create a baseline outside the app repo:

Compare relevant files:

Port only the specific scaffolder changes needed for the user’s goal. Do not replace the app wholesale or discard existing app logic.

Verification

Run the project’s normal checks after upgrading:

For backend function or upload-related changes, also test the OAuth-backed commands:

To verify the optional key-based path, set both DD_API_KEY and DD_APP_KEY before running the same commands.