releases/README.md indexes releases up to v2.4.1, but the repository is at v2.5.1 (fdf677a NodeNorm v2.5.0, 1d8f7be v2.5.1) and no releases/v2.5.x.md files exist.
This matters more than usual because the release notes are the only place that records which Babel build each NodeNorm version was released against — they are effectively the provenance ledger that /status's babel_version points into. A gap at the head of the chain means there is no written record of what 2.5.0/2.5.1 shipped or which Babel build they were validated with.
releases/README.mdindexes releases up to v2.4.1, but the repository is at v2.5.1 (fdf677aNodeNorm v2.5.0,1d8f7bev2.5.1) and noreleases/v2.5.x.mdfiles exist.This matters more than usual because the release notes are the only place that records which Babel build each NodeNorm version was released against — they are effectively the provenance ledger that
/status'sbabel_versionpoints into. A gap at the head of the chain means there is no written record of what 2.5.0/2.5.1 shipped or which Babel build they were validated with.