# Check Current Versions

> Verify current stable/LTS versions of runtimes, frameworks, and libraries before writing code. Use when starting a project or adding a dependency.

- Skill: `markcmarshall/check-current-versions` (Agent Skill)
- Install (CLI): `npx skillmds@latest add markcmarshall/check-current-versions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/markcmarshall/check-current-versions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: markcmarshall (https://skillmd.com/u/markcmarshall)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/markcmarshall/check-current-versions

---


# Check current versions

An LLM's sense of "current" is frozen at its training cutoff date. That's not a
reasoning failure, it's a property of the artifact — versions released and
patterns deprecated after the training cutoff are structurally unknowable to the model.

## Instruction

For every runtime, framework, and major library this project depends on:
determine the current official stable/LTS release by checking the
authoritative source (release page, registry, or LTS schedule) — never rely
on training data for "current," it's stale by construction.

Compare against what's pinned. Report each mismatch as `pin → available`,
tagged patch/minor (low-risk) or major (enumerate breaking changes before
recommending).

Never recommend moving onto a beta/RC/preview channel to chase "latest."
Where a runtime has a formal LTS track, prefer LTS over Current even when
Current is newer.