# How a memo becomes a release: what changed in v1.1.0, sgit.ai > The changes to the article "How a memo becomes a release" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [How a memo becomes a release](../../how-a-memo-becomes-a-release.md) / [Versions](../how-a-memo-becomes-a-release.md) / v1.1.0 # How a memo becomes a release: what changed in v1.1.0 From v1.0.0 (2026-10-21, `439de14d1`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 5 changed in place, 67 unchanged. About 0 words added and 98 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../how-a-memo-becomes-a-release.md) 2 unchanged paragraphs !shot pi-flow.webp | images/ | From a memo to a release,release in three stages: writing in the session,and checking in the session, andthen shipping on GitHub. A failed leak scan sends the work back to the first stage. | architecture 24 unchanged paragraphs, under In short {#in-short}, From voice to article {#write}, The checks in the session {#local}… !shot pi-ci.webp | images/ | The jobs on GitHub.GitHub:Aa push to devdev,validates, tests, tags and deploys. Aa pull request into mainmain,must beand a major. A push to main checks the major, tags it if needed, publishes a GitHub Release and deploys.main. | architecture 4 unchanged paragraphs, under How long each part takes {#time} !shot pi-time.webp | images/ | One release,release timed in seconds.seconds,Inin the session, the 18 tests are the longest step, then the cardssession and bannersonand sgit.ai's page build. On GitHub, the tests again.GitHub. | timeline 4 unchanged paragraphs, under What runs where, and what lasts {#where} !shot pi-where.webp | images/ | Where each part lives. The builders, tests, workflow and writing rules arelives: in the repository. The release script, graph writer, figure helpers and width check existrepository, only in this session;session,the behaviour policy and the leak scanor only in this container. | architecture 11 unchanged paragraphs, under What is redundant {#redundancy} !shot pi-split.webp | images/ | The proposed split:split between the session runsandwhatGitHub,only it can check, about 4 minutes; GitHub runswith the browsertimetests,eachaboutwould5. A change to the site's code runs the browser tests in the session too.take. | architecture 22 unchanged paragraphs, under What a new session would have {#new-session}, What this does not claim {#limits}, The diagrams, as source {#diagrams}… [all versions](../how-a-memo-becomes-a-release.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/how-a-memo-becomes-a-release/v1.1.0.html)*