fix(checks): duplicate-section spares the entries immutable freezes, and 1.3.1 #29

Merged

mikluko merged 2 commits from mikluko/duplicate-section-frozen into main

2026-09-10 20:43:29 +00:00

mikluko commented

2026-09-10 20:27:04 +00:00

(Migrated from github.com)

1.3.0 shipped duplicate-section at error against every entry, released ones included. On a released entry the finding asks for an edit release-entry-modified refuses, so between them the two checks describe a document that cannot exist: remove the duplicate and the notes differ from what the tag published, leave it and the run stays red. A repository carrying a duplicate anywhere in its history had no move that turned CI green.

The gate is the set immutable already walks, the entries the reference tag's changelog carried, rather than a second rule saying nearly the same thing. Two rules meant to agree drift; one set read by both cannot.

An entry the tag never carried is still checked. immutable admits it as a repair rather than a rewrite, so it is one someone may still edit, and a finding on it is one they can act on.

Verified against the document that hit this. uptime-com/up2-monitoring at release/v0.182.0-pre, against tag v0.181.2:

	findings
1.3.0	`:34` open entry, `:771` frozen since 0.180.2
this	`:34` only

1.3.0 shipped `duplicate-section` at `error` against every entry, released ones included. On a released entry the finding asks for an edit `release-entry-modified` refuses, so between them the two checks describe a document that cannot exist: remove the duplicate and the notes differ from what the tag published, leave it and the run stays red. A repository carrying a duplicate anywhere in its history had no move that turned CI green. The gate is the set `immutable` already walks, the entries the reference tag's changelog carried, rather than a second rule saying nearly the same thing. Two rules meant to agree drift; one set read by both cannot. An entry the tag never carried is still checked. `immutable` admits it as a repair rather than a rewrite, so it is one someone may still edit, and a finding on it is one they can act on. Verified against the document that hit this. `uptime-com/up2-monitoring` at `release/v0.182.0-pre`, against tag `v0.181.2`: | | findings | |---|---| | 1.3.0 | `:34` open entry, `:771` frozen since 0.180.2 | | this | `:34` only |