mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-09-21 14:22:14 +03:00

Files

BillyOutlast f6b314cf9d fix(cache): port #12885 truncated-completion write guard into dual-layer cache

Ports the single-layer cache's #12885 fix into both write paths of
the new dual-layer architecture: a response cut short by the output
token ceiling (finish_reason "length"/"max_tokens") is a partial
answer, not a reusable one, so it must never be written to the
semantic cache. Caching it under a temperature:0 signature pinned
the truncation for every later identical request.

- src/lib/semanticCache.ts: new isTruncatedCompletion() predicate.
- semanticCacheStore.ts / streamingSemanticCacheStore.ts: gate both
  the legacy setCachedResponse() write and the new dual-layer
  manager.store() write on it.

Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>

2026-09-16 02:17:58 -03:00

features

feat(proxies): show how many egress IPs actually served a proxy pool (#13581 )

2026-09-15 19:48:52 -03:00

fixes

fix(cache): port #12885 truncated-completion write guard into dual-layer cache

2026-09-16 02:17:58 -03:00

maintenance

fix(ci): clear the release/v3.8.51 base-reds left by the 09-15 batch (stryker, CLI i18n, paid-target fixture, call-log traceId, Jina prefix, callLogStats import, gitleaks) (#13747 )

2026-09-15 22:48:19 -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).