mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-09-21 06:12:17 +03:00

Files

Markus Hartung 2a50ce2088 chore(quality): rebaseline file-size caps the HouMinXi batch grew past

The nine PRs of that batch each measured their own growth correctly against
the tip they forked from, but three files were touched by more than one of
them, so the caps only broke once they were stacked:

  providers/page.tsx     2007 -> 2025  (#12504 CSV import errors + #12495 search)
  chatCore.ts            5981 -> 5984  (#12325 generic quota cache drop on 429)
  accountFallback.ts     2461 -> 2467  (#12566 on top of #12590's own rebaseline)

Measured on the release tip with all nine merged. Does not touch codex.ts or
stream.ts, which were already over their caps before this batch.

2026-09-03 12:48:55 -03:00

features

feat(providers): add SeekAi OpenAI-compatible New-API gateway (#12557 )

2026-09-03 12:46:06 -03:00

fixes

fix(quota): drop generic quota cache on upstream 429 (#12325 )

2026-09-03 12:38:39 -03:00

maintenance

chore(quality): rebaseline file-size caps the HouMinXi batch grew past

2026-09-03 12:48:55 -03:00

README.md

Release v3.8.47 (#6569 )

2026-07-13 09:12:40 -03:00

README.md

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).