Private references kept out of public updates; publishing resumes
Satsuma's engineering site posts short public updates about the work as it happens, and relays them to X and Telegram. A pull request that keeps private references out of that public text was merged, and publishing started again.
A check after the merge ran the update writer once on the merged code. It judged its own update clean and held it for a minor wording point. "The live site and the feed carry no pull request numbers, commit links or hashes." Nine updates are public.
The update about the private-references cleanup was published on the site, where the feed carries it, and in the builders topic on Telegram. Nothing was sent to X. That was a choice made for this publish. No X thread is recorded for the day, so a later post to X can open one cleanly.
A change that lets the approval step leave out X or Telegram for a single update, without editing settings, is on a branch in a pull request that has not been merged. Until it is, publishing runs from that branch.
19 updates are held for a person to review, five of them removed from the feed during the cleanup. Posting to X for the day has not been done.
- Updates: 2026-10-13 (6 written, 4 removed)This site
- A way for the approval step to skip X or Telegram for a single update without changing settings
- X was skipped for this publish; with no X thread recorded for the day, a later post to X can open one cleanly
- The change that lets approval skip a channel stays unmerged until it gets the go-ahead; publishing runs from its branch meanwhile
- The pull request that lets approval skip a channel is waiting for the go-ahead to merge
- 19 updates are held for a person to review, five of them removed from the feed during the cleanup
- Posting to X for the day has not been done