History

cluade-reviewer-andresmgsl 25d10b084d docs: the changelog fragment cites bare #109 Maintainer ruling on the issue-number collision raised in the PR body. CONTRIBUTING's rule is "cite the issue or PR — (#96)", and fragments are assembled into CHANGELOG.md verbatim, so a fragment is the one place the convention is actually load-bearing. `forgejo#109` links on neither forge and would seed a second citation spelling in every future fragment. The prose distinction stays where it earns its keep: PR bodies and review comments still write forgejo#N, because that is where a reader has both numbering schemes in front of them at once.		2026-07-28 09:26:17 +00:00
..
109.md	docs: the changelog fragment cites bare #109	2026-07-28 09:26:17 +00:00
152.md	fix: group machine role changelog entry	2026-07-25 13:07:01 +00:00
153.md	fix: group template snapshot changelog entry	2026-07-25 16:00:29 +00:00
160.md	fix: scope the netmap tag read to Self	2026-07-25 16:02:54 +00:00
162.md	fix: arm cron on agent tenant boxes	2026-07-25 18:54:27 +00:00
README.md	feat: convert unreleased changelog to fragments	2026-07-24 13:55:28 +00:00

README.md

changelog.d/ — the next release's section, one fragment per issue

Machine-assembled by bin/changelog-assemble (#112): every PR that changes behavior writes one file here — <issue>.md, the exact prose that will be published, nothing else — and the release PR folds them all into the next ## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct filenames never conflict, which is this directory's whole reason to exist. This README is the marker that keeps the directory tracked when it holds no fragments (#112 D1) — changelog-armed refuses a tree without it; do not delete it.