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

Files

diegosouzapw bdca029cbd fix(providers): route opencode-go/gpt-5.6-luna to /responses (#12196 )

opencode-go's static model registry was missing a gpt-5.6-luna entry, so
getModelTargetFormat() returned null and resolveOpencodeTargetFormat()
fell back to "openai", making OpencodeExecutor.buildUrl() post to
/chat/completions -- which the Go upstream 500s on for this model (it
only serves gpt-5.6-luna via /responses). The github provider already
declares targetFormat:"openai-responses" for the same model id, and
opencode-go itself already does the same for deepseek-v4-pro/flash.

Adds the missing registry entry mirroring those siblings.

2026-09-10 15:44:00 -03:00

features

feat(dashboard): orchestration canvas fase 3 — compare two runs in the History tab (2.9) (#12677 )

2026-09-10 10:15:52 -03:00

fixes

fix(providers): route opencode-go/gpt-5.6-luna to /responses (#12196 )

2026-09-10 15:44:00 -03:00

maintenance

docs(checks): keep doc counts honest — headings, rankings, catalog, weights, quality gate and scoring diagram now covered (#12507 )

2026-09-10 10:54:38 -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).