Skip to content

Give every repository the changelog block - #25

Merged
sehkone merged 1 commit into
mainfrom
sehkone/issue-24
Aug 9, 2026
Merged

Give every repository the changelog block#25
sehkone merged 1 commit into
mainfrom
sehkone/issue-24

Conversation

@sehkone

@sehkone sehkone commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Closes #24.

Five repositories — bootler, multifold, roxyd, aice-web-next, aimer-web — are gaining a CHANGELOG.md (aicers/bootler#221, aicers/multifold#96, aicers/roxyd#52, aicers/aice-web-next#923, aicers/aimer-web#921), so every repository in the organization keeps one. repos.json withheld the changelog block from exactly those five, which would leave them holding the file with no shared rules for maintaining it. STYLE.md asks the block to follow the file rather than lead it, and the file is arriving.

All twelve entries now include changelog.

This changes nothing downstream yet

None of the five consumes anything — no drift-check job, no pin file, no marker pairs. repos.json is intent, and intent has no effect on a repository until it is onboarded.

What it must not do is get ahead of the file. Onboarding one of them while it still has no CHANGELOG.md would hand it rules for a file that is not there, which is what deploy-core hit. #22 orders that work; each repository's CHANGELOG.md has to merge before its onboarding pull request opens.

Changelog link section

The changelog also gains what it should have had from 0.1.0: an ## [Unreleased] heading and the link reference section every other repository in the organization carries, so a reader can diff any two releases from the file instead of assembling compare URLs by hand.

Grade

PATCH. A rule newly applying to a repository is MINOR, and below 1.0.0 the grades shift down one. Nothing in blocks/ changes — which makes 0.1.2 the first release to depend on the guard fixed in #20: comparing blocks/ alone would refuse it.

Test plan

  • All twelve entries include changelog; repos.json parses
  • lint_blocks.py, test_render.py, test_apply_blocks.py, test_release_surface.py, test_sync.py, markdownlint — all pass

Five repositories -- bootler, multifold, roxyd, aice-web-next, aimer-web
-- are gaining a CHANGELOG.md, so that every repository in the
organization keeps one. repos.json withheld the changelog block from
exactly those five, which would leave them holding the file with no
shared rules for maintaining it. STYLE.md asks the block to follow the
file rather than lead it; the file is arriving, so the block follows.

Nothing reaches those five yet. None of them consumes anything -- no
drift check, no pin file, no marker pairs -- and repos.json is intent,
which has no effect on a repository until it is onboarded. What this must
not do is get ahead of the file: onboarding one of them before its
CHANGELOG.md merges would hand it rules for a file that is not there,
which is what deploy-core hit. #22 orders that work.

The changelog also gains what it should have had from the first release:
an Unreleased heading and the link reference section every other
repository here carries, so a reader can diff any two releases from the
file rather than assembling compare URLs by hand.

PATCH. A rule newly applying to a repository is MINOR, and below 1.0.0
the grades shift down one. Nothing in blocks/ changes -- which makes this
the first release to depend on the guard fixed in #20, since comparing
blocks/ alone would refuse it.

Closes #24
@sehkone
sehkone merged commit 0090d3a into main Aug 9, 2026
1 check passed
@sehkone
sehkone deleted the sehkone/issue-24 branch August 9, 2026 05:52
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.

repos.json withholds the changelog block from five repositories that now have the file

1 participant