Evidence record / flue
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3
GitHub Latest still points to 2.2.2 while npm latest is 2.3.0. npm published 2.3.0 without a matching GitHub Release. GitHub therefore still advertises @flue/cli@2.2.2 as its Latest release even though npm latest is 2.3.0. A watcher using only GitHub Releases receives no 2.3.0 release notice.
Channel: tagged-release (different current markers on GitHub Releases and npm). Half: defect. Date: 2026-10-13 (dated channel observation; GitHub release published 2026-09-28, npm 2.3.0 published 2026-10-12).
Operator consequence: Resolve the install version from npm and the root CHANGELOG at the version tag. GitHub’s Latest badge alone leaves a reader on 2.2.2, which lacks the finish-hook, local process-group and interceptor-identity fixes. A GitHub Release for the new stable or an explicit documented channel policy would settle the mismatch.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3
Source links
Primary links, including exact changelog lines when available.
- github release2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3withastro/flue / %40flue%2Fcli%402.2.2official docs2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3api.github.com/repos/withastro/flue/releases/latestofficial docs2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3registry.npmjs.org/@flue%2Fruntime/2.3.0tagged commit file2026-10-13-flue-github-latest-still-points-to-2-2-2-while-npm-latest-is-2-3withastro/flue / CHANGELOG.md#L3-L16
Versioned source: run artifact