# Versions of versions: what changed in v1.1.0, sgit.ai > The changes to the article "Versions of versions" 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) / [Versions of versions](../../versions-of-versions.md) / [Versions](../versions-of-versions.md) / v1.1.0 # Versions of versions: what changed in v1.1.0 From v1.0.0 (2026-10-18, `7b0b11b76`) to v1.1.0 (2026-10-18, this release), paragraph by paragraph. 0 paragraphs added, 0 removed, 1 changed in place, 38 unchanged. About 1 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../versions-of-versions.md) 1 unchanged paragraph Summary: Versioning is one of the things that works best on this site. Every release has a number and a note, every article has its versions and the differences between them, and that history helps everyone: me, to see what changed between sessions; readers, to see what is new; and agents, to understand what is going on before they build. Now parts of the site are big enough to need the same discipline on their own. The first is the section for publishers, which has grown from a page into something closer to a website of its own, with a specific audience, regular updates and an environment that has to be maintained. On 18 October it got the start of this: a version history for its page, with every version frozen and the differences shown block by block. The idea I wantwould like to name is the next step, versions of versions: the section gets its own version line, independent of the site's, and the site's release records which version of each part it carries. It is a tree, and it is fractal: a version can contain other versions, which contain their own. The newsroom will soon be built on the newsroom API, which already has two version lines of its own, so that connection needs tracking too. In time the home page and the article pipeline could work the same way, each area with its own releases, checks and quality bar. That part is coming later. This article is also an example of writing for an agent: the idea was in my head and nowhere the agents could find it, so now it is. 37 unchanged paragraphs, under In short {#in-short}, Why versioning works {#why}, The publishers' section needs its own {#publishers}… [all versions](../versions-of-versions.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/versions-of-versions/v1.1.0.html)*