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-2-3-0-returns-flue-to-export-style-releases-squashed-commits-from-a-source-tree-not-on-git

2.3.0 returns Flue to export-style releases: squashed commits from a source tree not on GitHub, a plain v-tag, the root CHANGELOG, and no GitHub Release. Four weeks after adopting Changesets (2.0.7, 2026-09-15), Flue dropped it. 2.3.0 reached the public repo as two squashed commits generated elsewhere. It has no per-change history, no PR and no GitHub Release, and the root CHANGELOG.md is the only release note (it again carries 2.0.7 through 2.3.0). The CHANGELOG does not mention the process change. Two behavior fixes rode inside the commit titled “chore: remove Changesets release tooling”: the finish-hook re-render in session.ts (section 6) and narrowed exports in document-attachments.ts. The public tree no longer holds the runtime, SDK, OpenTelemetry or Vite tests for the contracts the profile leans on: abort.test.ts, session-abort.test.ts, truncated-tool-call.test.ts, harness-tool-lineage.test.ts, tool-deadline.test.ts, mcp.test.ts, telemetry/content.test.ts and observe-bounded.test.ts are all gone. On 2026-10-12, between 06:59Z and 07:53Z, the lead maintainer closed 23 issues: 14 were converted to Discussions (feature requests, including conversation data deletion #764 -> discussion #855, submission retry #787 -> #844, bounded history in @flue/react #807 -> #840, LINE #798 -> #843 and WeChat #799 -> #842), 8 were fixed in 2.2.0 or 2.3.0, and 1 (#602) was closed as not reproducible. GitHub labels all 23 “completed”. Two closed issues were re-filed the same day as new open issues (#744 as #851, #669 as #850); #744 also became discussion #847. Feature requests continue in Discussions, where #855 (deletion for retention or erasure) remains open. CONTRIBUTING.md at v2.3.0 (no-PR policy unchanged in the window) describes the project as an experiment in which agents implement and a small team decides.

Channel: tagged-release. Half: defect. Date: 2026-10-12.

Operator consequence: Track Flue by its v tags and the root CHANGELOG at each tag. GitHub Releases and per-package changelogs have stopped, and the per-package files no longer exist. An issue closed as “completed” is not evidence that anything shipped; feature requests now live in Discussions, including open deletion request #855. Per-change public commits and regression tests no longer cover the runtime contracts here, so inspect the release diff and run your own tests for the contracts you depend on: abort repair, tool timeouts, trace redaction, history windows. The verification work that public PRs and CI used to do now falls on you. Commit ancestry, which this watchlist uses to resolve channels, now resolves only to whole releases for Flue.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-flue-2-3-0-returns-flue-to-export-style-releases-squashed-commits-from-a-source-tree-not-on-git

Profile citations

  • Flue / claim / export-style-release
  • Flue / posture / governance

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact