Skip to content

fix: support Linear changelog coverage - #432

Merged
levifig merged 1 commit into
mainfrom
fix/linear-changelog-coverage
Nov 2, 2026
Merged

levifig merged 1 commit into
mainfrom
fix/linear-changelog-coverage

Conversation

@levifig

@levifig levifig commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Linear-based projects can declare native issues in the changelog coverage check. It accepts short Linear URLs and matching issue-key links, while retaining GitHub reference rules and checks for changed Unreleased notes.

Real Markdown list paragraphs own their links and source spans. Images, HTML attributes, code examples and comment-split spellings cannot provide coverage, and unchanged nested notes cannot credit new unlinked entries.

Verification

  • Full local verification passes with Go 1.27.3 and Node 24.20.0: uncached Go tests, compile checks, vet, CGO-free build, all 39 adapter tests and generated-content checks.
  • The required pinned-toolchain vulnerability audit passes.
  • Focused declaration, Markdown, real-Git CLI/body/event/pre-PR and release-only tests pass.
  • Author and independent falsification checks detect weakened entry ownership, old-note rejection, Unreleased boundaries and canonical source syntax.
  • Read-only checks against a real consumer’s immutable commits accept matching changed coverage and reject unchanged notes, wrong references and missing coverage.
  • Independent correctness and documentation review is clean.

Scope

Goldmark v1.8.7 is the only new module. Exact canonical source syntax remains required; coverage remains structural. Native issue identity, complete scope and accurate prose still require independent review.

The Go security prerequisite landed in #431. Broader dependency choices, including in-house alternatives, belong to #428. The existing journal ordering defect is captured separately in #430.

No provider calls, tracker configuration changes, runtime activation, release or deployment are included.

Ship

The signed candidate passed local gates and independent review. Landing requires successful hosted checks, the unchanged reviewed candidate and completed Verification boxes on #427.

Closes #427.

Agent notes
  • Head: 550ef82eac99dccee605c2d88885b261b8aeb674; tree: dd0ad102ada07c55114da94abf1b2a4ea1e82499; base: 5d6d7bfe0e7335b173fe1de6c587673a05dd2cfe.
  • Full Go 1.27.3 verification ran on this exact tree. Advancing the task-owned branch onto the landed prerequisite preserved its index and files; the resulting diff contains only these eight feature files.
  • Both review sides use the same original-document entry parser. CRLF is normalized before section and source-offset calculations. Canonical links are checked against original source bytes.
  • Earlier failed attempts remain recorded. They are not substituted for the final passing full gate or audit.
  • Only public code and synthetic examples are included.

Recognize real canonical issue links and keep changed-note checks scoped to their source entries.

Fixes #427.
@levifig
levifig marked this pull request as ready for review November 2, 2026 21:17

levifig commented Nov 2, 2026

Copy link
Copy Markdown
Owner Author

Approved for landing. The signed Linear-reference checker passes full local verification, the pinned Go 1.27.3 vulnerability audit, independent review and all hosted checks. No runtime activation, release or deployment is included.

Agent notes
  • Reviewed head: 550ef82eac99dccee605c2d88885b261b8aeb674; tree: dd0ad102ada07c55114da94abf1b2a4ea1e82499; actual base: 5d6d7bfe0e7335b173fe1de6c587673a05dd2cfe. GitHub reports a valid signature and author me@levifig.com.
  • Accept Linear issue references in structural changelog coverage #427: canonical Linear declarations and exact issue-key links pass. Missing, unchanged, copied, mismatched and example-only coverage fails. GitHub repository/reference rules, release-only behavior and independent semantic review remain intact.
  • Full uncached Go tests, compile/vet/CGO-free checks, 39 adapter tests, generated-content checks and the required pinned audit pass on this exact tree. The landed Go prerequisite has the independently reviewed tree and green resulting-main CI.
  • Author and independent falsification cover old notes, entry ownership, Unreleased boundaries and canonical source syntax. Final actual eight-file diff and prose review are clean.
  • The committed base/head coverage check passes. The binary names Go 1.27.3, this revision and an unmodified source tree. Read-only consumer tests on immutable commits accept matching new notes and reject unchanged notes, wrong references and missing coverage.
  • All four Verification boxes are ticked. Hosted build and both emitted changelog runs pass.
  • Native rules require PRs, signatures, linear history and squash; check contexts remain advisory in native rules. Ship requires them to pass regardless.
  • The maintainer explicitly authorized Ship. Merge must pin this head, preserve the reviewed tree and use squash with a deliberate outcome message.
  • Broader dependency review Review runtime dependencies and compare in-house alternatives #428 and the pre-existing journal timestamp defect Order journal blocker outcomes correctly across timestamp precision #430 remain open. No risk or unrelated issue is silently marked fixed.

@levifig
levifig merged commit faa76e9 into main Nov 2, 2026
3 checks passed

levifig commented Nov 2, 2026

Copy link
Copy Markdown
Owner Author

Landed as faa76e95; the resulting-main build passed. #427 is closed with all Verification boxes satisfied. No installed runtime, release or deployment was changed.

Agent notes
  • Landed tree dd0ad102ada07c55114da94abf1b2a4ea1e82499 matches the reviewed and tested candidate. GitHub verifies the signature and author me@levifig.com.
  • Local reconciliation remains pending because main belongs to the owner checkout, which contains local configuration. That checkout was preserved. Clean feature worktrees and local/remote feature branches are retained.
  • Remote landing and native issue closure are verified independently of that local synchronization boundary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Accept Linear issue references in structural changelog coverage

1 participant