mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-08-17 20:52:15 +03:00

Files

Diego Rodrigues de Sa e Souza f8879cd4e6 feat(usage): add TTFT/E2E-latency/tokens-per-second to model latency stats (#6875 )

Widen getModelLatencyStats() to also compute avgTtftMs, avgE2ELatencyMs and
avgTokensPerSecond from usage_history's existing ttft_ms/tokens_output
columns (no schema change), and feed them into buildAutoCandidates() so the
existing speed-ranking factor (#6011, speedRanking.ts/routerStrategy.ts)
scores on real telemetry instead of falling back to the pool median.

avgE2ELatencyMs aliases avgLatencyMs: usage_history has no distinct second
latency column beyond latency_ms/ttft_ms.

Extracted the accumulation/reduction logic into pure helpers
(accumulateLatencySample, buildLatencyStatsEntry, resolvePositiveOption) in
usageHistory/helpers.ts to keep getModelLatencyStats() under the complexity
ratchet and usageHistory.ts under its frozen file-size baseline.

2026-07-17 14:57:53 -03:00

features

feat(usage): add TTFT/E2E-latency/tokens-per-second to model latency stats (#6875 )

2026-07-17 14:57:53 -03:00

fixes

fix(providers): cap grok-cli tools at 200 for cli-chat-proxy (#6986 )

2026-07-17 10:52:26 -03:00

maintenance

chore(quality): re-baseline file-size for #7213 analytics route + #7603 audio test (v3.8.49 campaign own-growth)

2026-07-17 13:28:44 -03:00

README.md

feat(release): changelog.d/ fragments — eliminate the CHANGELOG merge-storm cascade (#6783 )

2026-07-10 07:22:49 -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).