mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-21 06:12:17 +03:00
Mid-cycle reconciliation of `## [3.8.51]` against the full cycle range `release/v3.8.50..release/v3.8.51` (091589089c..d6f315018a, 696 non-merge commits): - fold the 366 `changelog.d/` fragments into the section (features had been landing under `[Unreleased]` because the aggregator appends at the FIRST matching heading) and delete them - drop 25 fragments that duplicate bullets already shipped in `[3.8.50]` / `[Unreleased]` (six phantom fragments re-added by branches cut before the v3.8.50 aggregation; 19 pre-cycle PR fragments) - generate one bullet per cycle commit that had no fragment (350 commits: 44 features / 196 fixes / 91 maintenance, 17 Dependabot bumps rolled up), carrying the merged PR link and `— thanks @author` - credit audit: link every fragment to the PR that actually landed it (`git log --diff-filter=A`), fix three `#PR_NUMBER` placeholders and two misnumbered fragments (#11845, #11864), credit the recreated PRs to their original authors (#11887–#11892 → @MumuTW, #12255 → @backryun, #11771 → @Rahulsharma0810), the nine hartmark co-authored fixes, and the deleted PR #11370 to @kriptoburak - add the "Release by the numbers" block, the Top-25 ranking (mailmap + GitHub login) and the mandatory `### 🙌 Contributors` hall (111 external contributors + maintainer, generated by `release:contributors --inject`) - resync the 41 i18n CHANGELOG mirrors Gates: check:changelog-integrity OK, check:docs-sync PASS.
changelog.d/ — changelog fragments
A PR never edits CHANGELOG.md directly during the cycle. Instead it adds ONE new
file here — its changelog entry as a fragment. Two PRs never touch the same file, so
changelog merge conflicts (the "CHANGELOG-eat" cascade that forced a re-sync push + full
CI re-run after every sibling merge) are structurally impossible.
Convention
| Directory | Aggregates under |
|---|---|
features/ |
### ✨ New Features |
fixes/ |
### 🐛 Bug Fixes |
maintenance/ |
### 📝 Maintenance |
- Filename:
<PR-number>-<short-slug>.md(e.g.fixes/6700-dockerfile-better-sqlite3.md). The PR number prefix keeps aggregation order deterministic. - Content: the exact bullet line(s) that should land in
CHANGELOG.md, starting with-. Multi-line (continuation) bullets are fine. Keep the repo's credit format:(#PR — thanks @user). - One fragment per PR (rarely more, e.g. a PR that both fixes and adds).
Example
changelog.d/fixes/6496-cloudflare-relay-worker-syntax.md:
- **fix(providers):** Cloudflare relay Worker deploys use Service Worker syntax with `body_part` metadata ([#6496](https://github.com/diegosouzapw/OmniRoute/pull/6496)) — thanks @SeaXen
Aggregation
The release captain (or /generate-release) folds all fragments into CHANGELOG.md and
deletes them:
node scripts/release/aggregate-changelog.mjs # write + delete fragments
node scripts/release/aggregate-changelog.mjs --dry-run # preview only
Fragment well-formedness is enforced by npm run check:changelog-integrity (the same
gate that guards against CHANGELOG-eat for legacy direct edits).