How severity works

StackTrace Weekly reads the changelogs of 30 developer tools and classifies every release. Classification is AI-assisted against this fixed rubric, then two deterministic code checks run before anything is published: prereleases are capped at FYI, and no item is marked CRITICAL without a verbatim quote from the release notes proving the change. We bias toward the lower severity when uncertain, and never inflate to fill space.

🔴 CRITICAL

A reader running this tool in production must read it before their next deploy: a breaking change to a stable public API/default in a stable release, a security fix on stable, or a deprecation/EOL with a removal deadline within 90 days. Always backed by a direct quote.

🟡 NOTABLE

Worth knowing, no action this week: new stable features, GA of a beta, distant deprecations, significant performance/pricing changes, or a breaking change that only lands in a prerelease.

⚪ FYI

Everything else: patches, docs, DX polish, dependency bumps, and all alpha/beta/rc/canary releases without a headline feature. Multiple patch releases of one tool are collapsed.

← back to issues