Plan a low-risk dependency upgrade | DevPrompt Lab

Assess breaking changes, security impact, lockfiles, and verification before upgrading.

workflow · Dependencies · intermediate

English Tiếng Việt

A dependency workflow that relies on official release notes and project tests instead of guessing compatibility.

Reusable content

Plan the dependency upgrade. Verify the current and target versions, supported runtime, official release notes, security advisories, peer dependencies, and lockfile behavior. Identify breaking changes that affect this repository. Recommend the smallest version step that meets the goal, then list code changes, focused tests, full checks, and rollback method. Do not run package scripts from an untrusted dependency without review. If the target version or compatibility evidence cannot be verified, state that before proposing implementation.

Package: {{PACKAGE}}

Current version: {{CURRENT_VERSION}}

Target version: {{TARGET_VERSION}}

Upgrade policy: {{POLICY}}

How to use it

Use official package docs and release notes for current version-sensitive claims.

Example

Before: capture lockfile diff. After: run typecheck, unit tests, production build, and the package's documented compatibility suite.