Coding & developmentDependency maintenancecode

Prepare evidence before upgrading a dependency

Maps API changes, lockfile effects and rollback for a package update.

Editorial illustration for this prompt; the prompt itself does not generate this image.

Ready to use

Prompt

For [DEPENDENCY], [CURRENT VERSION] and [TARGET VERSION], inspect official release notes, if accessible, and the repository's real usage before proposing changes. If release notes or repository access is missing, list the needed evidence and do not claim the update was assessed. List breaking APIs, transitive updates, affected files, tests to run and rollback steps. Separate verified release-note facts from inferred risks. Do not claim current security status without a dated authoritative source or install the update without permission. Provide a patch plan and validation matrix. Check that the lockfile resolves the intended version and that tests cover the feature paths that use the package.