Home / About / Engineering / v0.12.80: @newsroom.writer: A revision is a republish
Engineering · release
v0.12.80: @newsroom.writer: A revision is a republish
v0.12.80: @newsroom.writer: A revision is a republish
| Version | v0.12.80 · the version row |
| Date | 2026-10-16 |
| Kind | patch |
| File | admin/engineering/releases/v0.12.80.md |
A new house rule, from the owner: a revised article is written as if it were published for the first time. The reader gets the current article; the evolution is in the version history and its diffs, and in the release notes.
Scion and sgit loses its "What changed in this version" section and the revision narrative in its summary, In short and figures; the facts stay, said plainly (the CDN does not yet serve object reads from cache; the 59-second small-vault clone was a Lambda limit, fixed on the CLI's development branch). The two companion articles' sources no longer frame them as following a review. Four older articles had the same pattern and now state the current fact instead: Handing secrets to agents and Hooks are kernel code lose their dated correction notes; A policy beside the prompt and Stop the bleeding name their second memo as a source rather than as a version 1.1. Your own newsroom's house rules now say a correction is a new version with its diff. The writing guide in admin/content/articles/README.md carries the rule.
The cards (0)
| Id | Kind | Priority | Title | Release | Status |
|---|
For an agent
Release v0.12.80 of newsroom.sgit.ai on 2026-10-16: 0 card(s): .