The sync-back section prescribed a direct push that the default branch has refused since
the ruleset Require PR on default branch: a sync-back lands through a pull request merged
with a merge commit, which scripts/release/sync-next-cycle.mjs opens since #20645.
New section Landing on a release branch: omni-queue. In shadow mode a manual merge waits
for the queue's verdict on the PR's final head (green checks prove a PR against the base
they ran on: #19132); in live mode the label is the landing.
* feat(ci): omni-queue owner voice and signed merge commits, both off
Owner voice (config `voice`, default "app"): with "owner", the queue's
comments and label removals on pull requests, the dashboard issue and its
comments, base-red comments and the tree-divergence issue go out with
OMNI_QUEUE_LAND_TOKEN (scripts/merge-queue/voice.mjs). Reads, commit
statuses, refs, the state branch and re-runs stay the App's. A missing
token or a 401/403 retries the same write with the App's token and records
one error event per tick. commentOnce trusts markers by the App or by the
owner's login read from the token itself (GET /user).
Signed merge commits (config landing.signing, default "none"): with "ssh"
and landing.actor "owner", composeCandidate signs every merge commit with
the key the tick job writes from the OMNI_QUEUE_SIGNING_KEY secret to a
0600 file under RUNNER_TEMP (removed by an always() step). git gets the
path as per-command configuration through the environment. A missing key
or a failed signature composes unsigned and records one error event per
batch.
The shipped config keeps both off and mode shadow.
* docs(changelog): add the fragment for the omni-queue owner voice and signed merges (#20792)
* test(ci): compare the signed commit's committer by prefix, not a built regex (#20792)
The retired-asset audit in provider-assets-generic-fallback.test.mjs walked the
working tree at module load and read every text file whole. In the omni-queue
base check, "Fast Quality Gates" builds config/quality/test-impact-map.json
(gitignored, ~556 MB on release/v3.8.55) before running the whole unit suite,
and readFile(path, "utf8") on it threw "RangeError: Invalid string length"
(run 44795004759).
The audit now lists files with git ls-files (same scope rules; the old walk
stays as the fallback for a tree without git metadata), reads each file with a
64 MiB bound, and reports oversized or unreadable files by name instead of
aborting. A regression test builds a temporary git repository with an
untracked 600 MB sparse file in a walked directory.
* fix(gamification): commit one XP award as a single transaction
An authenticated request ran six autocommit statements per award: addXp inserted
xp_audit_log and upserted xp_action_counts and user_levels, then
updateRewardScores upserted leaderboard for global, weekly and monthly. Each took
the writer lock and its own commit, and a failure between them left XP without a
score or the reverse.
awardXp wraps addXp and the leaderboard upserts in one db.transaction.
emitGamificationEvent and the bonus-XP path (streak_bonus, badge_unlock) use it,
and the leaderboard credit now follows the award directly. Anti-cheat still runs
before any write; the lifetime action counter, one-time badge and streak-bonus
guards, tokens_shared scope and score values are unchanged. No setting or
delayed batch is added, so no award can be lost on shutdown.
Finding: ordata-48.
(cherry picked from commit a6517e5416cfbbb8e692767e68b0548dce931369)
* perf(db): compute the migration 044 key backfill once per connection
The old statement ran two correlated GROUP BY / ORDER BY subqueries for every
usage_history row that missed api_key_name, so the cost was the missing rows
times the history of their connection. The most used name and id of each
connection now go into two temp tables once, and the update joins them. The
values filled are the same: the most used non-empty value wins, a count tie
goes to the greater value, name and id are picked independently, a row with no
connection is not touched, and an unknown connection stays empty. Only installs
that have not run 044 yet see the change.
Finding: ordata-92.
(cherry picked from commit cb61850859b9e571c6cfbc6471349bdbb0048f54)
* fix(usage): retry a locked usage write on a backoff before dropping the row
A usage row that met a locked database was retried once after 1 s, then
dropped with one console.error. The 2 s busy timeout is not waited on the
first attempt, so a second writer process (CLI, desktop host) that holds the
lock for a few seconds lost the billing row.
The usage writer now retries on a 1, 2, 4, 8, 16 s backoff (about 31 s in
all), off the request path as before. Non-lock errors are still logged at
once and never retried. The generic one-retry scheduler used by call logs
and proxy logs is unchanged.
Finding: sub2api-86
(cherry picked from commit 93dd20bdd69b5cc23d836575c93c03172edca1f8)
* fix(quota): a stale exhausted sample with no reset no longer pauses an account
An exhausted quota window that carries no future reset time and was last seen
more than 2 hours ago now reads as unknown, not as reached. A paused account
receives no fresh quota headers, so one old sample kept it paused forever.
A window with a future reset still pauses until that reset, and a window seen
within 2 hours still pauses.
Finding: sub2api-43.
(cherry picked from commit e0b51b8052e42e475e8554d904b3f96223f181a1)
* fix(usage): add a late row to a purged day's rollup instead of replacing it
The retention job rolls usage_history up into daily_usage_summary, then deletes
whole days. The next rollup replaced a day's summary with the raw rows it still
found, so one row that arrived late for a purged day erased that day's earlier
totals (3 requests became 1 in the probe).
The purge now records the day it reached and the highest row id at that time in
one key_value row (no migration). A row below that day with a higher id is late:
the rollup adds it to the day's summary and moves the recorded id forward in the
same transaction. A second rollup that read the same rows finds the mark changed,
rolls back, and reports an error, so the caller keeps its raw rows. Days that are
not purged yet are still recomputed from their raw rows.
Finding: sub2api-82.
(cherry picked from commit 449f4f3b10f117e2e25716abd302ee0641949968)
* chore(changelog): name the new fragments 0000-<slug> for the publisher
* refactor(db): move the usage purge day recording into two helpers
The late-row member adds a branch and a transaction to deleteWholeDaysBefore.
That raises its cognitive complexity from 0 to 1 over the base. Two small helpers
keep the function at its old complexity. No behaviour change.
* docs(changelog): number the fragment (#20226)
* chore: drop derived values the release refresh now owns
Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.
* test(usage): stop waiting for a MockTimers warning newer Node versions never emit
The retry test waited at the top level for the experimental-feature
warning that the first mock.timers.enable() prints, so a later test that
counts console.error lines would not see it. Node 24 (the CI runtime) no
longer emits that warning, so the wait never settled and the runner
failed the whole file with 'unsettled top-level await'. Wait one
macrotask instead: on versions that still warn, the warning (queued on
process.nextTick) has passed by then; on versions that do not, the wait
ends at once.
* revert(quota): drop the stale-sample no-pause fix from this bundle
Reverts 9a2da1815d (fix(quota): a stale exhausted sample with no reset no
longer pauses an account), with its changelog fragment and test.
Replaced by a separate PR with a per-session/opt-in design (see the PR list); dropped here so the two do not conflict.
* fix(usage): bound late rows to the read max id and check the purge mark on every rollup write
- The late-row branch of the rollup SELECT is bounded by the MAX(id) it read,
so a row another process commits between the two reads waits for the next
run instead of being counted now and again after the mark moves to maxId.
- A rollup transaction that only replaces summaries now checks the purge mark
it classified the days with and rolls back when a purge or a late-row add
moved it, so a stale read cannot overwrite a day that gained late rows.
* revert(db): drop the migration 044 backfill rewrite from this PR
044 is a merged migration: databases that already recorded it never run the new SQL, and a merged migration keeps its content. Removes the SQL change, its changelog fragment and its test, as the maintainer asked. The other changes in this PR are unchanged.
---------
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
Caller-supplied poll_interval_ms, timeout_ms and poll_timeout_ms on the
NanoBanana, Magnific, Black Forest Labs and RenderHour image handlers are
clamped (30 s interval, 10 min window) by a shared helper that never
shortens a default. The RenderHour poller passes the request abort signal
to sleep(). applySyntxProviderRules only runs own entries of the rules
table.
POST /api/settings/local-corpus (rootPath) and POST /api/settings/obsidian/webdav
(vaultPath) now require an operator credential (dashboard session or local CLI) through
requireOperatorCredential; API keys of any scope and access tokens get 403. The webdav
route passes alwaysRequireAuth because /api/settings/obsidian is ALWAYS_PROTECTED.
Both roots also refuse the filesystem root, the home directory itself and the system
directories /etc /usr /bin /sbin /var /proc /sys /dev /boot /root (and below), compared
after path.resolve and realpath, with a fixed 400 message. The vault keeps its DATA_DIR
overlap refusal.
isInternalAdmissionBypass() accepted the bypass header together with a
bearer equal to resolveSelfLoopBearer(), which is the deployment env key
when one is configured. That key is an ordinary API key clients hold, so
it proved nothing about where a request came from.
Apply the rule from #19292: only the per-process self-hop token (held in
memory on globalThis, compared in constant time) grants the bypass and
the internal upstream-start cap. The vision bridge describe call, the
only caller that sends the bypass header, now also sends the token; it
only does so for this process's own listener.
Engine: google. Sources: docs/architecture/QUALITY_GATES.md, docs/ops/BRANCHING_MODEL.md, docs/ops/MERGE_TRAIN.md, docs/ops/RELEASE_CHECKLIST.md, docs/ops/RUNNER_BOX.md. 299 mirror file(s). 31 unit(s) failed and were left as they were.
Run: https://github.com/cheaper-inference/OmniRoute/actions/runs/44793361106
The default setup moved CodeQL 2.27.4 -> 2.27.5 on 2026-11-20; the release/v3.8.55 JS analysis went 236 -> 339 results with the same 87 rules and no code change, opening 101 alerts at once and failing the codeql ratchet on every PR. Owner-authorized temporary ceiling 6 -> 103 while the security wave triages them; a follow-up lowers it to the measured count.
#18336 dropped the lcov reporter from the coverage merge on pull_request while SonarQube was off; once vars.SONARQUBE_ENABLED came back, the scan found no coverage/lcov.info and every PR showed 0.0% coverage on new code. The merge step now writes lcov on a PR when SonarQube is enabled (measured cost: none beyond runner variance), and the sonarqube job fails before the scan when the file is missing. Closes#20725.
On the Firecrawl cloud endpoint, a wait_for_selector that is a plain
non-negative integer is now sent as the v2 waitFor delay in milliseconds,
capped at the v2 limit of 60000. Any other value still goes through the
wait action as a CSS selector. Self-hosted base URLs keep the v1 body.
The mapping moves into applyWaitForSelector() so firecrawlFetch does not
grow. Adds the changelog fragment for the v2 scrape migration (#19636).
Grafted from #19799 (numeric waitFor handling and changelog entry), with
the integer-only rule and the 60000 ms clamp from the review.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Apply the #20567 status contract to the subscription/plan quota text
signals ("usage limit reached", "plan limit", weekly/session usage
limits). On a 400 such a phrase now counts only with a structured
credit/quota code or for the message-only allow-listed providers
(command-code, bai, openai-compatible-*), so a phrase repeated from the
request no longer classifies as QUOTA_EXHAUSTED or puts a shared LLM or
search connection on hold. 429, 403 and every other status are
unchanged.
The status rule is extracted from isCreditsExhaustedForStatus into
quotaTextSignalCountsForStatus and reused by the classifier, the
fallback engine and the search cooldown.
POST /api/plugins/marketplace/install downloads plugin code and may activate it,
so it now requires the management credential in every auth mode
(alwaysRequireAuth), like POST /api/plugins.
PUT /api/plugins/[name]/config now validates the body with
validatePluginConfig(): only keys declared in the plugin's configSchema are
stored, with type, range and enum checks. A plugin without a configSchema has
no configurable keys, so the write is refused with a fixed 400 and nothing is
stored.
Exclusion is decided before the account-cooldown check, so an account that
the fallback loop just excluded could turn its short model lockout into the
reported model cooldown even while the account itself was cooling down for
much longer, and the caller would retry too early. Count an excluded account
only when it is not in an account cooldown, with the regression test from
#20249.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
* chore(ci): retire the Mergify merge queue
The owner retired Mergify from the merge process on 2026-11-19.
- .mergify.yml: drop the release and relay-integration queue rules and
the queue-label cleanup rule; keep the file with commands_restrictions
that refuse every Mergify command that merges or rewrites a PR, since
with no configuration Mergify's implicit queue still merges on
@mergifyio queue.
- dry-run-lts-cut G11 now checks omni-queue: valid config at the source,
bases managing the release branch, mode live, label present.
- Dated notes on the Mergify-era docs; G11 rows updated.
* docs(changelog): add the fragment for the Mergify retirement (#20616)
* chore(quality): record the retired Mergify contract in the test-masking allowlist (#20616)
* fix(release): sync-next-cycle opens a PR instead of pushing to the release branch
release/vX+1 is the default branch and ruleset 21899981 (Require PR on
default branch, no bypass actors) refuses a direct push, so the final
push of the sync-back could never land. The script now pushes the merge
commit to chore/sync-back-main-<sha12> and opens a PR into the release
branch; it never merges it. Re-running after the side branch reached
origin prints the open PR (or opens it) and stops. The old push stays
behind --direct-push (off by default). The sync worktree is detached at
origin/<branch>, so the merge commit never moves a local release branch
ref. The release-green gate and --skip-green-gate are unchanged.
* docs(changelog): add the fragment for #20645
* test(release): compare the sync-back next-steps line exactly (#20645)
The text form of the usage command (@@om-usage and the plain
/api/usage/om-usage) now applies the same account rule as the JSON form:
a key without self:account-quota or a management scope sees only its
personal quota, and the shared provider accounts are not read for it.
Keys with self:account-quota, management keys and the environment key
keep the provider quota.
"different targets share the existing request wait allowance" had two timing
faults with ~110-320 ms of slack each:
- A wait is granted only when (cooldown end - now + 50 ms) <= maxWaitMs. With a
480 ms cooldown and maxWaitMs 480, a stall that delayed the cooldown write until
the reread made the first wait ~530 ms, so the first target stopped without
spending the allowance and the second used it (200 !== 502).
- A stall after the write let the 480 ms cooldown lapse before the reread
(~160 ms later), with the same result.
The cases now use a 2 s cooldown and, for the budget variant,
maxWaitMs = budgetMs = 2.6 s: any first wait fits (1.4-2.05 s under a 500 ms
stall on either side) and what is left never covers a second one.
Reproduced on the old file with injected stalls (250 ms before the write: the
budget variant fails; 520 ms after it: both fail) and passing on the new one in
all three conditions, together with control runs that give room for two waits
(default limits, and budgetMs 5.2 s): both targets then wait and the request
succeeds (200, four calls), so the 502 still comes from the shared limit.
Full file: 69/69.
The fragment was keyed by the issue number (20250-auggie-cli-quiet-flag.md);
changelog.d fragments are keyed by the PR number, so it becomes
20272-auggie-cli-quiet-flag.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The node tests in this PR exercise the request-body builder, the schema and
the validator directly; on the current base they pass because the fix (#19384)
is already merged. This jsdom test renders AddApiKeyModal for cloudflare-ai,
types an API key and an Account ID, clicks "Check" and asserts the request to
/api/providers/validate carries the trimmed accountId. It fails with the
#19384 change reverted (the body has no accountId) and passes with it.
The changelog fragment is renamed to the <PR>-<slug> convention and moved to
maintenance: the fix itself already has its entry under #19384, so this PR
only adds regression tests.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Add the resolveModelDisplayName cases from #20114: an explicit name such as
"Custom Label" wins over a dated snapshot id, and the id passed as its own
name is still derived to "GPT-5". Also cover the namespaced
cmc/openai/gpt-4.1-2025-04-14 id.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The existing #20449 case passes on the base too: the entry-relative worker is
found before any module-relative candidate, so the guard is never exercised.
This case leaves only a cwd-relative TypeScript worker, so the base (which
ignores moduleUrl and keeps using the real module directory) returns the
source tree's worker, while the fix skips every module-relative candidate and
probes only the cwd layout.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named api-key-usage-limits-long-context-20153.md;
changelog.d fragments are keyed by the PR number first, so it becomes
20255-api-key-usage-limits-long-context.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The five wall-clock assertions used a 250 ms budget, which a loaded CI runner
can exceed even with the linear fix. The pre-fix regexes take tens of seconds
on the same inputs, so a shared 2 s budget still fails on the old code and
passes on the fix. Also names the changelog fragment after PR #19916, as
changelog.d/README.md asks.
Guards the opt-in contract of targetModels/excludedModels: with both lists unset
or empty, every model is still routed by task type and counted in the stats,
and a persisted config written before #20294 (no scoping keys) hydrates without
adding a scope.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named cursor-grok-47-standard-speed-20077.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20248-cursor-grok-47-standard-speed.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fallback loop can also pass the account that just failed through the
excludeConnectionIds array option, not only the positional argument. Add a
test for that entry point (adapted from #20249, which used the option name
excludedConnectionIds that getProviderCredentials does not read), and add the
changelog fragment for #20083 based on the wording from #20249.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named dashboard-fmt-compact-boundary-20068.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20113-dashboard-fmt-compact-boundary.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Exclusion is decided before any quota check, so an excluded account whose
quota for the model is exhausted could still turn its short lockout into the
reported model cooldown, and the caller would retry too early. Count an
excluded account only when its quota still allows the model, with a
regression test where both accounts are exhausted.
Keeps resolveCallLogArtifactWorker under the cyclomatic complexity cap
(15) flagged by the complexity-ratchets new-code gate; lookup order and
fallbacks are unchanged.
targetModels/excludedModels now cover the exact id plus its ":" variants
and "/" children, so scoping openai/gpt-4o no longer captures
openai/gpt-4o-mini (#20294).
The bounded `.{0,N}?` repeats still backtracked when a long whitespace run
followed SELECT, import or if (SELECT plus 140k spaces took ~2 s; if plus
140k spaces did not finish), and they stopped scoring valid spans longer
than the cap.
Count the import/SELECT/${} indicators with a linear scan that keeps the
old greedy one-per-line semantics, and make the if ... then condition start
at a non-space so no two whitespace quantifiers overlap. Each span indicator
is now asserted on its own, including spans past the old caps.
- Reject `compaction_trigger` on Chat Completions targets again: Codex remote
compaction v2 needs exactly one `compaction` output item, which a Chat upstream
cannot return, so skipping the marker answered with an unusable normal turn
(and a trigger-only input produced `messages: []`).
- Restore readable compaction items with role-aware text parts (`output_text`
for assistant), so the Codex normalizer no longer forwards assistant history
as `input_text`.
- Accept only non-blank string content or a non-empty part array, falling back
to `text`; other shapes are no longer forwarded as Chat content.
- Split restoreReadableCompactionItem into helpers (complexity ratchet).
Refs #19730
The multi-key and solitary-thought branches pushed consumePlanningLeak
over the cognitive-complexity limit (complexity-ratchets new-code 0 -> 1).
Extract classifyUnclosedObject, isSolitaryThought and
classifySolitaryThought; behavior is unchanged (the repeated top-level
comma check in the unclosed branch was already covered by the early
return).
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
#19384 already landed the same accountId forwarding in the validate
request body, the Zod schema and the route. Merging the base made both
copies coexist (duplicate accountId keys in an object literal and in the
schema), so drop this branch's duplicates and keep the base code; the
regression tests pass against it unchanged.
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
During fallback, the account that just failed is excluded from the retry and
tagged "excluded", so the #18664 branch (which only checked "modelLocked")
skipped its short retryable lockout. When every other account was
quota-exhausted, the request was reported as "All <provider> accounts have
exhausted their quota" with a reset minutes or days away, and clients backed
off for that long although the healthy account recovered within seconds.
Also consider "excluded" connections in that branch. Excluded connections
without an active retryable lockout are still ignored.
Fixes#20083
v2 scrape reads waitFor as a millisecond delay, so the selector string cannot
go there. The v2 actions list has a wait step that blocks until a CSS selector
is visible, which is what the field meant. A self-hosted base URL still speaks
v1 and keeps the selector in waitFor.
Signed-off-by: Minxi Hou <houminxi@gmail.com>
Firecrawl shuts its v1 API down on 2026-12-10 and answers it with HTTP 410
after that. Search, map and credit usage already call v2. The page fetch and
the dashboard key probe were the two calls still posting to /v1/scrape.
The cloud host now posts to /v2/scrape. v2 scrape rejects maxDepth outright and
treats waitFor as a millisecond delay, so the depth and CSS selector fields
stay on our own request but are no longer forwarded to the cloud. A
self-hosted base URL still speaks v1, so it keeps /v1/scrape and both fields.
Fixes#19636
Signed-off-by: Minxi Hou <houminxi@gmail.com>
echo "::error::coverage/lcov.info is missing or empty after downloading coverage-report; SonarQube would report 0% coverage on new code. Check the lcov reporter in the test-coverage job's merge step (#20725)."
- feat(routing): allow scoping task-aware routing to specific target or excluded models/combos via `targetModels` and `excludedModels` in TaskRoutingConfig (#20294)
- **feat(ci):** omni-queue can speak as the owner and sign its merge commits, both off by default. With `voice: "owner"` in `config/merge-queue/config.json`, the queue's comments and label removals on pull requests, the dashboard issue and its comments, base-red comments and the tree-divergence issue go out with `OMNI_QUEUE_LAND_TOKEN`; statuses, refs, the state branch, re-runs and reads stay the App's, and a missing or refused token falls back to the App with one `error` event. With `landing.signing: "ssh"` (owner actor only), every merge commit the queue composes is signed with the owner's key from the `OMNI_QUEUE_SIGNING_KEY` environment secret, and a missing key composes unsigned with one `error` event per batch ([#20792](https://github.com/cheaper-inference/OmniRoute/pull/20792))
- Move the Firecrawl cloud scrape call and the dashboard key probe from `/v1/scrape` to `/v2/scrape` before the 2026-12-10 v1 shutdown (#19636): a CSS `wait_for_selector` becomes a v2 `wait` action, a plain integer becomes the `waitFor` delay in milliseconds (capped at 60000), and `maxDepth` is no longer sent to the cloud endpoint. Self-hosted base URLs stay on `/v1/scrape` with the previous body.
- **fix(translator):** translate Responses `compaction` input items carrying readable content or text into standard Chat messages (assistant summaries keep `output_text` parts) instead of rejecting them. Previously, compaction items without `ocx1:` bridge encryption were rejected with `400 unsupported_feature`, causing combo fallbacks to fail for Responses-native clients. Remote compaction (`compaction_trigger`) still fails explicitly on Chat Completions targets, since they cannot return the required `compaction` output item ([#19730](https://github.com/cheaper-inference/OmniRoute/issues/19730)).
- **auto-combo**: Count the `import … from`, `SELECT … FROM` and `${…}` code indicators in `detectCodeComplexity` with a linear scan, and stop the `if … then` pattern in `detectReasoningDepth` from backtracking across long whitespace runs, eliminating quadratic backtracking on long lines without dropping long valid spans (#19881)
- **fix(sse):** Consider fallback-excluded accounts with short retryable model lockouts when checking remaining accounts for quota exhaustion, returning the short lockout cooldown instead of a multi-hour quota reset; an excluded account that is in an account cooldown or whose own quota for the model is exhausted is still ignored ([#20084](https://github.com/cheaper-inference/OmniRoute/pull/20084), [#20083](https://github.com/cheaper-inference/OmniRoute/issues/20083)) — thanks @bojackduy and @rafacpti23
- Roll over compact count formatting (`fmtCompact`) to `M` and `B` at rounding boundaries (e.g. 999,950 to `1.0M` and 999,999,999 to `1.0B`) to prevent displaying `1000.0K` or `1000.0M` in analytics and dashboard counts (#20068).
- **fix(gamification):** One XP award (audit row, action counter, level row and the global, weekly and monthly leaderboard scores) is now a single SQLite transaction instead of six separate commits per authenticated request, and a failure part-way no longer leaves XP without a score. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- **fix(usage):** A usage row that arrives late for a day the retention job already rolled up and deleted is now added to that day's summary. Before, the next rollup replaced the day's totals with the late row alone and the earlier requests vanished from the analytics. The job records the day it purged to and the highest row id it counted, in one settings row (no migration). ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- **fix(usage):** A usage row whose write meets a locked database (for example a second writer process on the same file) is now retried on a backoff for about 31 seconds before it is dropped, not once after one second, so a billed request no longer ends with no usage row. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- Allow standard-speed Grok 4.7 variants (`medium`, `low`, `xhigh`) and bare effort aliases to use standard speed by omitting `ModelDetails` and setting `reasoning_effort`, preventing Cursor from falling back to `grok-4.7-high-fast` (#20077).
- **fix(providers):** remove the deprecated `--quiet` flag from the Auggie CLI invocation arguments ([#20250](https://github.com/cheaper-inference/OmniRoute/issues/20250)). Auggie CLI 1.2+ removed the `--quiet` option, which previously caused all requests to fail with `Error: Unknown option: --quiet` and a 502 status code.
- **fix(callLogs):** guard call-log artifact worker path resolution when build-time `import.meta.url` is not a valid local file URL on Windows ([#20449](https://github.com/cheaper-inference/OmniRoute/issues/20449))
- **fix(release):** `scripts/release/sync-next-cycle.mjs` no longer pushes the sync-back straight to the release branch, which ruleset 21899981 refuses on the default branch: it pushes the merge commit to `chore/sync-back-main-<sha12>` and opens a PR into the release branch (land it as a merge commit), re-runs find the open PR instead of creating another, and the old push stays behind `--direct-push` ([#20645](https://github.com/cheaper-inference/OmniRoute/pull/20645))
- Apply the same account rule to the text form of the usage command (`@@om-usage`): keys without `self:account-quota` or a management scope see only their personal quota, and the shared provider accounts are not read for them.
- **fix(security):** Marketplace plugin installs need a management credential in every auth mode, and plugin config writes only accept the keys the plugin declares in its config schema (a plugin without a schema has no writable config)
- **fix(security):** an HTTP 400 counts subscription/plan quota wording ("usage limit reached", "plan limit", weekly/session usage limits) as quota exhaustion only when the structured error code is a credit/quota code or the provider documents a message-only 400 form (`command-code`, `bai`, `openai-compatible-*`), the same contract as #20567, so such a phrase echoed from the request no longer puts a shared LLM or search connection on hold
- **fix(security):** Choosing the local corpus root (`POST /api/settings/local-corpus`) or the Obsidian WebDAV vault (`POST /api/settings/obsidian/webdav`) now needs a dashboard session or the local CLI: API keys and access tokens of any scope get 403. Both routes also refuse the filesystem root, the home directory itself and system directories (`/etc`, `/usr`, `/bin`, `/sbin`, `/var`, `/proc`, `/sys`, `/dev`, `/boot`, `/root`) with a fixed 400 (CodeQL #1371, #1372, #1373)
- **fix(security):** The internal chat admission bypass and the internal upstream-start cap are granted only on a per-process token held in memory; the deployment env key (`OMNIROUTE_API_KEY` / `ROUTER_API_KEY`) still authenticates requests but no longer marks them as internal
- **fix(security):** Image generation on NanoBanana, Magnific, Black Forest Labs and RenderHour caps a caller's `poll_interval_ms` at 30 s and `timeout_ms` / `poll_timeout_ms` at 10 minutes (defaults unchanged), and RenderHour stops waiting between polls when the request is aborted; SYNTX provider rules only run for names defined in the rules table, so an `ai_name` such as `constructor` or `__proto__` no longer reaches an inherited `Object.prototype` member (CodeQL #1389, #1392) ([#20824](https://github.com/cheaper-inference/OmniRoute/pull/20824))
- **fix(ci):** Preserve all eight V8 coverage shards with lossless transport, verified manifests and explicit checkout-path relocation before the native c8 report. Bind generated TSX code and source maps from exclusive producer caches before projecting a proven filename layout, and archive the preparation receipt. Support partial reruns by selecting successful producer jobs and immutable artifact IDs while retaining their original attempts. Reject incomplete, duplicate, corrupted or unproven evidence and empty coverage without changing coverage thresholds.
- **test(providers):** regression tests for the Cloudflare Workers AI "Check" button sending the Account ID to `/api/providers/validate` (#19304, fixed in #19384) ([#19851](https://github.com/cheaper-inference/OmniRoute/pull/19851)) — thanks @rafacpti23
- **chore(ci):** retire the Mergify merge queue: `.mergify.yml` drops the `release` and `relay-integration` queues, the auto-merge label condition and the label-cleanup rule, and refuses the Mergify commands that merge or rewrite a pull request; rail gate G11 of `release:dry-run-lts-cut` now checks omni-queue (valid config, release branch managed, mode `live`, label present) ([#20616](https://github.com/cheaper-inference/OmniRoute/pull/20616))
- **fix(ci):** SonarCloud gets `coverage/lcov.info` on pull requests again — the coverage merge skipped the lcov reporter on PRs since #18336, so every PR showed 0.0% coverage on new code; the SonarQube job now also fails clearly when the file is missing ([#20769](https://github.com/cheaper-inference/OmniRoute/pull/20769))
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.