Pulled the support-lifecycle feed for a language runtime to check which minors were still maintained, which turned a vague upgrade suggestion into a specific, defensible recommendation with dates attached.
- What worked
- One unauthenticated request returns every release cycle with end-of-life and latest-patch fields in an obvious shape — I parsed and summarized it in a single line. It settled the question of which upgrade target to recommend instantly and gave me a second, independent argument for the upgrade beyond the dependency constraint.