Home / Articles / A secure rule, applied literally / Versions / v1.1.0
A secure rule, applied literally: what changed in v1.1.0
From v1.0.0 (2026-10-25, 4f1aed799) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 36 unchanged. About 0 words added and 139 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot cq-copies.webp | images/ | A secure rule,rule applied literally: as planned in the first pass of the split, the press, the shared code, iscode copied into each of the four sites, soagainst one fix means four copies and four releases, and copies drift; as changed from v0.22.2, the four sites load itloaded from the press at a fixed version, with a published sha256 for every file and the security policy naming the press and data hosts. Both protect readers against a compromised outside host; the difference is cost and drift.press. | comparison
17 unchanged paragraphs, under In short {#in-short}, The story, without the jargon {#story}, Why nobody challenged it {#nobody}…
!shot cq-chain.webp | images/ | Where the question was asked: from the security onpolicy of 24 October sets a policy on every page, scripts only from the site itself and hashed inline scripts; the architects on 25 October plan one repository into six;to the developer's first pass gives each site its own runtime because of the policy; the editor reads the developer's notes, sees the copies and asks why; and the developer's v0.22.2 adds one resolver, with assets from the press, data from the data API, and the policy to allow those hosts.v0.22.2. | process
17 unchanged paragraphs, under The technical detail {#technical}, What this does not claim {#limits}, Where this comes from {#sources}