Dependency update

Shorten a package-update note to compatibility, evidence, and remaining work.

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.

Example

Dependency upgrade review

Before 94 words

This pull request proposes updating queue-client from 2.4.1 to 3.0.0. We need the new server-side cancellation API. Upstream 3.0.0 requires Node.js 20 or later and removes the retryDelay option in favor of retryDelayMs. Our application already uses Node.js 22, and this PR renames that option without changing its value of 500. All 146 unit tests passed locally on Linux. The integration suite did not run because its test broker was unavailable. Upstream says reconnect handling is improved, but we have not verified that behavior in our application. The update is not merged or deployed.

After 50 words

Change: Proposed queue-client 2.4.1 → 3.0.0 for server-side cancellation; not merged or deployed. Impact: Requires Node.js ≥20; app uses 22. retryDelay becomes retryDelayMs; value remains 500. Validation: 146 unit tests passed locally on Linux. Upstream reconnect improvements are unverified here. Remaining work: Integration suite could not run; test broker unavailable.

Examples illustrate the method. They do not measure model output.

Files and sources

prompt.txt Complete prompt as plain text.
SKILL.md The same prompt with a skill header.
llms.txt (JSON) Prompt, metadata, example, and sources.
LICENSE MIT license text.

An original sho.rten.it skill. Source notes.