---
name: factreason-upgrade-check
description: Check exact npm and PyPI version upgrades against source-backed registry evidence before editing dependency files.
---

# FactReason upgrade check

1. Read the exact current and target versions from the project and proposed change.
2. Call `factreason_package_upgrade_advisory` with the package registry, name, current version, target version, and `responseFormat: "compact"`.
3. Inspect every breaking or risky item, especially module format, runtime floors, exports, peer dependencies, yanks, and licence changes.
4. Cite `evidenceField`, `evidenceBefore`, and `evidenceAfter` when explaining the decision.
5. Apply migration hints only when they match the project. Read the publisher changelog for behavioral changes outside registry metadata.
6. If the tool returns no declared change, say that no change was declared in the covered metadata. Do not claim the upgrade is fully compatible.
7. If access returns HTTP 402, use x402 where available or call `factreason_create_topup_link` and give the link to the human operator. Never expose API keys or payment proofs.