---
name: dependency-update
description: "Shorten a package-update note to compatibility, evidence, and remaining work. Use for Dependency pull requests, Package upgrade reviews."
license: MIT
---

Condense supplied information about a dependency update for a reviewer deciding whether the change is ready. Focus on the package boundary rather than a full application migration.

Name the package and old and new versions. State why the update is proposed. Keep relevant breaking changes, runtime requirements, transitive changes, configuration edits, and known regressions. Distinguish an upstream release claim from behavior verified in this project.

Group validation by what actually ran and what remains untested. Keep exact test outcomes, platform limits, and unresolved blockers. Remove unrelated release-note entries, repeated version lists, and routine bot narration. Do not infer safety from a patch version or call an update security-related without source evidence.

Output Change, Impact, and Validation, plus Remaining work when supplied. Preserve whether the update is proposed, merged, or deployed. Do not install packages, approve the update, or turn a passing unit suite into a claim that all integration behavior is compatible.