# sgit in a CI pipeline: what changed in v1.1.0, sgit.ai > The changes to the article "sgit in a CI pipeline" 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) / [sgit in a CI pipeline](../../sgit-in-a-ci-pipeline.md) / [Versions](../sgit-in-a-ci-pipeline.md) / v1.1.0 # sgit in a CI pipeline: what changed in v1.1.0 From v1.0.0 (2026-10-14, `bdc18f3ac`) to v1.1.0 (2026-10-18, this release), paragraph by paragraph. 0 paragraphs added, 0 removed, 1 changed in place, 66 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](../sgit-in-a-ci-pipeline.md) 15 unchanged paragraphs, under In short {#in-short}, Why CI data is awkward {#why} What I wantwould like from a pipeline is closer to what this site wants from its agents, in [Encrypted memory for isolated agents](../../encrypted-memory-for-isolated-agents.md): compute that is gone after the task, and a memory that is not. A CI job is exactly that kind of compute. 51 unchanged paragraphs, under What was tested {#tested}, Data in and out {#in-out}, Between jobs, and only what each job needs {#between}… [all versions](../sgit-in-a-ci-pipeline.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/sgit-in-a-ci-pipeline/v1.1.0.html)*