check_stack
Identify required upgrades for your running components by comparing versions against curated release facts, revealing security fixes, breaking changes, and deprecations. Versions stay local.
Instructions
Check the user's running component versions against known facts. Versions are compared LOCALLY — only project slugs are sent to the ratatosk server, running versions never leave this process. Returns, per component, the facts from releases NEWER than the running version (the upgrade path). Default is a briefing: summary counts, critical/high facts in action_required, one line each for the rest, and the same advisory fixed on several release branches collapsed into one entry. Use detail:"full" for every fact verbatim (capped at 50 per component with relevant_facts_omitted — narrow with severity_min or target_version), target_version to limit to one upgrade hop, severity_min to filter. Components with zero facts carry tracked:true|false — tracked:false means the project is NOT covered by ratatosk, so the absence of facts is no-coverage, not safety. In brief mode, facts sharing one quoted sentence are merged with their ids listed together. Drill down with get_release or facts_by_entity.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| detail | No | brief (default): summary + critical/high facts + one-liners for the rest; full: every fact verbatim | |
| components | Yes | the running stack to check | |
| severity_min | No | only facts at or above this severity: info|low|medium|high|critical |