Compare commits

..

2 Commits

Author SHA1 Message Date
diegosouzapw
52f3d43f0b docs(changelog): add the fragment for #20629
Co-authored-by: Dizzle <112548150+maxmad64bis@users.noreply.github.com>
2026-11-19 10:07:30 -03:00
diegosouzapw
f5d94311f4 fix(ci): diff the OpenCode plugins against the commit npm last published
The plugin auto-bump compared each plugin folder with the previous release
tag only. A plugin change from a release whose plugin publish failed or never
ran (the v3.8.54 E404s) is already present at the next release's previous
tag, so that release sees no diff and the change never reaches npm.

The baseline is now the gitHead npm recorded for the plugin's latest version.
git diff compares trees, so the commit only has to be in the full-history
checkout (fetch-depth: 0). With no gitHead, a value that is not a commit id,
or a commit the checkout lacks, the step warns and falls back to the previous
release tag, as before. A registry failure on that lookup fails the step,
like npm_has_version. The version-allocation loop is unchanged.

The executed bump-step test gains an earlier untagged commit and a fake
`npm view <pkg>@latest gitHead`, with cases for: a change since the published
commit that the previous tag already had (bumps; the tag alone did not), no
change since the published commit (skips), no gitHead (tag fallback with a
warning), an unknown or malformed gitHead (tag fallback with a warning), and
a registry error on the lookup (fails).

Based on #20297.

Co-authored-by: Dizzle <112548150+maxmad64bis@users.noreply.github.com>
2026-11-19 10:04:17 -03:00
2206 changed files with 101689 additions and 100009 deletions

View File

@@ -1579,7 +1579,7 @@ PROVIDER_LIMITS_SYNC_SPACING_MS=1500
#OMNIROUTE_EMERGENCY_FALLBACK=true
# Reasoning cache cleanup cadence (ms). Default: 1800000 (30m). Floor: 60000.
# Used by: open-sse/services/reasoningCache.ts (auto-cleanup started on import).
# Used by: src/lib/jobs/reasoningCacheCleanupJob.ts.
#OMNIROUTE_REASONING_CACHE_CLEANUP_INTERVAL_MS=1800000
# Recover from a reasoning_effort 4xx whose body names no accepted set, by
@@ -1639,13 +1639,11 @@ PROVIDER_LIMITS_SYNC_SPACING_MS=1500
# on real disk. Used by: scripts/check/check-install-upgrade.mjs. Default: <repo>/.install-upgrade.
#OMNIROUTE_INSTALL_UPGRADE_WORKDIR=/var/tmp/omniroute-install-upgrade
# Already-packed npm tarball for the check:pack-artifact, check:pack-boot and
# check:install-upgrade release gates (same as their --tarball flag). check:pack-artifact
# validates this file's own entries and size instead of running `npm pack --dry-run`; the
# other two install it instead of running `npm pack`. Each first checks its package.json
# name/version match the repository's; the npm-publish workflow packs once and hands the
# file to all three. Unset, each gate packs the tree itself. Used by:
# scripts/build/validate-pack-artifact.ts, scripts/check/check-pack-boot.mjs,
# Already-packed npm tarball for the check:pack-boot and check:install-upgrade release
# gates (same as their --tarball flag). The gate installs this file instead of running
# `npm pack`, after checking its package.json name/version match the repository's; the
# npm-publish workflow packs once and hands the file to both gates. Unset, each gate
# packs the tree itself. Used by: scripts/check/check-pack-boot.mjs,
# scripts/check/check-install-upgrade.mjs. Default: unset.
#OMNIROUTE_PACKED_TARBALL=/path/to/omniroute-x.y.z.tgz
@@ -2419,11 +2417,6 @@ CURSOR_USER_AGENT="Cursor/3.4"
# or `interval` (one low-frequency check per stream; fires within the stall budget + 1-5s).
# Used by: open-sse/utils/streamStallWatchdog.ts.
# SSE_STALL_WATCHDOG=timer
# Heartbeat backpressure bound (#19640): after this many consecutive heartbeat ticks in which
# the client consumed nothing (the stream queue stayed full), the heartbeat timer stops and the
# stream is errored as abandoned. Any upstream chunk resets the count. Positive integer; invalid
# or unset = 8 (about 2 minutes at the 15s heartbeat interval). Used by: open-sse/utils/sseHeartbeat.ts.
# SSE_HEARTBEAT_MAX_UNCONSUMED=8
# ── Stream idle detection ──
# STREAM_IDLE_TIMEOUT_MS=600000 # Max silence between SSE chunks (default: 600000)
@@ -4318,12 +4311,6 @@ QUOTA_STORE_DRIVER=sqlite
# are ignored and reported once at startup. Empty with the allowlist enabled =
# nobody is served.
# TELEGRAM_ALLOWED_USER_IDS=
# Mini App initData anti-replay (#19833). Off by default (opt-in): when true, a verified
# (initData hash, message) pair is remembered in memory until the initData expires (24h after
# auth_date) and an exact repeat is rejected with 401. The Mini App reuses one initData for the
# whole session, so with it on a user who sends the same message twice ("ok") also gets a 401.
# The HMAC signature and the auth_date past/future bounds are always enforced.
# TELEGRAM_INITDATA_ANTI_REPLAY=false
# ── OmniConductor bridge (Conductor PRD RF1) ──────────────────────────────────
# Mirrors the OmniConductor hub's tasks into the local A2A TaskManager via SSE.

30
.github/workflows/base-ci-repair.yml vendored Normal file
View File

@@ -0,0 +1,30 @@
name: Release base repair
on:
push:
branches: [fix/release-v3.8.52-basereds]
permissions:
contents: read
jobs:
regression:
runs-on: ubuntu-latest
timeout-minutes: 12
env:
CI: "true"
OMNIROUTE_SKIP_SYSTEM_TRUST: "1"
DISABLE_SQLITE_AUTO_BACKUP: "true"
NEXT_TELEMETRY_DISABLED: "1"
PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: "1"
OMNIROUTE_MAX_TEST_WORKERS: "2"
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
with:
fetch-depth: 0
persist-credentials: false
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020
with:
node-version: "24"
- name: Verify old failure and final guarded transport
run: node scripts/check/base-ci-repair.mjs
- name: Clean owned state
if: always()
run: rm -rf -- .ci-work/base-ci-repair

View File

@@ -38,9 +38,6 @@ env:
# system TLS). Belt-and-suspenders with tests/_setup/isolateDataDir.ts.
OMNIROUTE_SKIP_SYSTEM_TRUST: "1"
CI_NODE_VERSION: "24"
# The V8 manifests require the producer and aggregator to have the same Node
# patch. A floating major can resolve to different patch versions on runner caches.
CI_V8_NODE_VERSION: "24.22.3"
CI_NODE_24_VERSION: "24"
CI_NODE_26_VERSION: "26"
@@ -1175,7 +1172,7 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_V8_NODE_VERSION }}
node-version: ${{ env.CI_NODE_VERSION }}
- uses: ./.github/actions/prepare-unit-storage
with:
cache: ${{ github.event_name == 'pull_request' }}
@@ -1195,7 +1192,6 @@ jobs:
- name: Unit tests (shard ${{ matrix.shard }}/8) with V8 coverage
env:
TEST_SHARD: ${{ matrix.shard }}/8
TMPDIR: ${{ runner.temp }}/v8-tsx-${{ github.run_id }}-${{ github.run_attempt }}-${{ matrix.shard }}
# NODE_OPTIONS (nao so o flag em test:unit:ci:shard) porque quem estoura o
# heap e o processo `c8` que embrulha a suite — ele agrega ~577 MB de JSON
# de cobertura bruta. Subir o teto so no node filho deixa o pai no default
@@ -1205,12 +1201,6 @@ jobs:
run: |
trap 'status=$?; { df -h "$GITHUB_WORKSPACE" "$RUNNER_TEMP"; du -sh coverage-shard; } || :; exit "$status"' EXIT
rm -rf coverage-shard coverage-shard-report
# Capture the transforms this producer actually executes; a reused or
# shared TSX cache cannot establish generated-layout provenance.
node scripts/ci/prepare-v8-coverage.mjs init-cache "$TMPDIR" "$TEST_SHARD" "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE"
V8_CACHE_PRELOAD="$(node -p 'require("node:url").pathToFileURL(process.argv[1]).href' "$GITHUB_WORKSPACE/scripts/ci/atomic-tsx-cache.mjs")"
V8_NATIVE_PRELOAD="$(node -p 'require("node:url").pathToFileURL(process.argv[1]).href' "$GITHUB_WORKSPACE/scripts/ci/native-worker-v8-layout.mjs")"
OMNIROUTE_CI_SYNC_TSX_CACHE="$TMPDIR" NODE_OPTIONS="$NODE_OPTIONS --import=$V8_CACHE_PRELOAD --import=$V8_NATIVE_PRELOAD" \
npx c8 --merge-async \
--temp-directory=coverage-shard \
--reports-dir=coverage-shard-report \
@@ -1218,23 +1208,11 @@ jobs:
--exclude=tests/** \
--exclude=**/*.test.* \
npm run test:unit:ci:shard
- name: Package successful shard coverage
env:
TEST_SHARD: ${{ matrix.shard }}/8
TMPDIR: ${{ runner.temp }}/v8-tsx-${{ github.run_id }}-${{ github.run_attempt }}-${{ matrix.shard }}
run: node scripts/ci/prepare-v8-coverage.mjs pack coverage-shard coverage-shard-upload "$TEST_SHARD" "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE" "$TMPDIR"
- name: Upload complete shard coverage
- name: Upload raw shard coverage
if: always()
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7
with:
name: coverage-shard-${{ github.run_attempt }}-${{ matrix.shard }}
path: coverage-shard-upload/
compression-level: 0
if-no-files-found: error
- name: Preserve raw coverage from failed shards
if: failure()
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7
with:
name: failed-unit-coverage-${{ github.run_attempt }}-${{ matrix.shard }}
name: coverage-shard-${{ matrix.shard }}
path: coverage-shard/*.json
if-no-files-found: error
@@ -1337,9 +1315,6 @@ jobs:
# the release gate can still exercise them via workflow_dispatch when needed).
test-coverage:
name: Coverage
permissions:
contents: read
actions: read
runs-on: ubuntu-latest
# 10min was sized before #7114 added the lcov reporter (Codecov/Sonar need it);
# merging 8 shard JSONs + text+json+lcov now takes ~10-12min — three consecutive
@@ -1379,47 +1354,41 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_V8_NODE_VERSION }}
node-version: ${{ env.CI_NODE_VERSION }}
- uses: ./.github/actions/npm-ci-retry
with:
# PR acceleration is not release-candidate provenance.
cache: ${{ github.event_name == 'pull_request' }}
- name: Select coverage producers for this attempt
id: coverage_selection
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
mkdir -p coverage
node scripts/ci/select-v8-coverage.mjs coverage/coverage-selection.json 8
- name: Download all shard coverage
uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8
with:
artifact-ids: ${{ steps.coverage_selection.outputs.artifact_ids }}
pattern: coverage-shard-*
path: coverage-shards/
merge-multiple: false
merge-multiple: true
- name: Merge + report + gate
# Verify and merge each raw report in order without storing a second
# raw copy. c8 reads the aggregate for source mapping and reporting.
# lcov on a PR only when SonarQube runs (#20725). #18336 (2026-10-26) dropped it on
# pull_request because its only PR consumer was the informational Codecov upload while
# SonarQube was off; once vars.SONARQUBE_ENABLED came back the `sonarqube` job scanned
# with no coverage/lcov.info and every PR showed 0.0% coverage on new code. Without
# Sonar the PR gate still only needs the json/text summaries, so lcov stays skipped.
# Merging 8 shards of raw v8 coverage is memory-heavy. `--merge-async`
# keeps the V8 coverage merge incremental instead of loading every raw
# JSON blob into one in-memory merge, which avoids Node heap OOMs.
# lcov only outside pull_request (2026-10-26): its sole consumer on a PR was the
# informational Codecov upload below (SonarQube is off: vars.SONARQUBE_ENABLED is
# unset), and the PR gate only needs the json/text summaries. The step took ~21 min
# on a measured PR against the org's 20-job hosted cap.
env:
NODE_OPTIONS: --max-old-space-size=8192
EVENT_NAME: ${{ github.event_name }}
SONARQUBE_ENABLED: ${{ vars.SONARQUBE_ENABLED }}
RUN_HEAD_SHA: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
run: |
LCOV_REPORTER=()
if [ "$EVENT_NAME" != "pull_request" ] || [ "${SONARQUBE_ENABLED:-}" = "true" ]; then
LCOV_REPORTER=(--reporter=lcov)
fi
if [ "$EVENT_NAME" != "pull_request" ]; then LCOV_REPORTER=(--reporter=lcov); fi
mkdir -p coverage
# Retained producers keep their original attempts. The receipt binds all
# eight job/artifact identities and the aggregate sent to c8.
node scripts/ci/prepare-v8-coverage.mjs prepare coverage-shards coverage-shards-verified 8 "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE" coverage/coverage-selection.json "$RUN_HEAD_SHA" "$GITHUB_REPOSITORY" > coverage/coverage-preparation.json
cat coverage/coverage-preparation.json
first_coverage_file=""
if [ -d coverage-shards ]; then
first_coverage_file="$(find coverage-shards -maxdepth 1 -type f -name '*.json' -print -quit)"
fi
if [ -z "$first_coverage_file" ]; then
echo "::error::No raw coverage shard data was downloaded."
find . -maxdepth 3 -type f | sort
exit 1
fi
# Gate aligned to the project's local coverage bar: `npm run test:coverage`
# gates at 60/60/60/60, so CI must match it (the previous CI floor of 40
# silently undershot the local bar — a real drift). Real merged coverage is
@@ -1427,7 +1396,7 @@ jobs:
# coverage ratchet (quality-baseline.json) layers "must not drop vs baseline"
# on top of this floor.
npx c8 report \
--temp-directory coverage-shards-verified \
--temp-directory coverage-shards \
--reports-dir coverage \
--merge-async \
--reporter=text-summary \
@@ -1437,7 +1406,6 @@ jobs:
--exclude=**/*.test.* \
--check-coverage \
--statements 60 --lines 60 --functions 60 --branches 60
node scripts/ci/prepare-v8-coverage.mjs verify-report coverage
- name: Build coverage summary
if: always()
run: |
@@ -1488,8 +1456,6 @@ jobs:
path: |
coverage/coverage-summary.json
coverage/coverage-report.md
coverage/coverage-selection.json
coverage/coverage-preparation.json
coverage/lcov.info
if-no-files-found: warn
@@ -1518,17 +1484,6 @@ jobs:
with:
name: coverage-report
path: coverage/
# Without lcov.info the scan still "succeeds" and publishes 0.0% coverage on new code
# (#20725): fail here, naming the cause, instead of letting the quality gate blame the PR.
- name: Require coverage/lcov.info for the scan
if: ${{ github.event_name == 'pull_request' && env.SONAR_TOKEN != '' && env.SONAR_HOST_URL != '' }}
run: |
if [ ! -s coverage/lcov.info ]; then
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)."
ls -la coverage || true
exit 1
fi
echo "coverage/lcov.info: $(wc -l < coverage/lcov.info) lines"
- name: Explain SonarQube skip
if: ${{ github.event_name != 'pull_request' || env.SONAR_TOKEN == '' || env.SONAR_HOST_URL == '' }}
run: |

View File

@@ -569,3 +569,5 @@ jobs:
with:
version: ${{ needs.validate.outputs.version }}
tag: latest
secrets:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

View File

@@ -284,24 +284,17 @@ jobs:
merge-multiple: true
# Use the immutable workflow revision, not the target checkout (which may
# predate these installers). Quick requires the workflow pair; full also
# requires security scanners.
- name: Prepare pinned quality scanners
# predate this installer). Both scanners are required even for --quick.
- name: Prepare pinned workflow scanners
id: workflow_scanners
env:
WORKFLOW_SHA: ${{ github.workflow_sha }}
EVENT_NAME: ${{ github.event_name }}
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
installers=$(mktemp -d "${RUNNER_TEMP:?}/quality-scanners-installers.XXXXXX")
git show "${WORKFLOW_SHA}:scripts/ci/install-workflow-scanners.sh" > "$installers/install-workflow-scanners.sh"
if [ "$EVENT_NAME" = "push" ]; then
bash "$installers/install-workflow-scanners.sh"
else
git show "${WORKFLOW_SHA}:scripts/ci/install-quality-scanners.sh" > "$installers/install-quality-scanners.sh"
bash "$installers/install-quality-scanners.sh"
fi
installer=$(mktemp "${RUNNER_TEMP:?}/workflow-scanners-installer.XXXXXX")
git show "${WORKFLOW_SHA}:scripts/ci/install-workflow-scanners.sh" > "$installer"
bash "$installer"
- name: Release-green validation (full)
id: validate
@@ -590,23 +583,17 @@ jobs:
path: suite-results
merge-multiple: true
# main can predate the installers: materialize both from the workflow SHA.
- name: Prepare pinned quality scanners
# main can predate the installer: obtain tooling from the workflow SHA.
- name: Prepare pinned workflow scanners
id: workflow_scanners
env:
WORKFLOW_SHA: ${{ github.workflow_sha }}
EVENT_NAME: ${{ github.event_name }}
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
installers=$(mktemp -d "${RUNNER_TEMP:?}/quality-scanners-installers.XXXXXX")
git show "${WORKFLOW_SHA}:scripts/ci/install-workflow-scanners.sh" > "$installers/install-workflow-scanners.sh"
if [ "$EVENT_NAME" = "push" ]; then
bash "$installers/install-workflow-scanners.sh"
else
git show "${WORKFLOW_SHA}:scripts/ci/install-quality-scanners.sh" > "$installers/install-quality-scanners.sh"
bash "$installers/install-quality-scanners.sh"
fi
installer=$(mktemp "${RUNNER_TEMP:?}/workflow-scanners-installer.XXXXXX")
git show "${WORKFLOW_SHA}:scripts/ci/install-workflow-scanners.sh" > "$installer"
bash "$installer"
- name: Main-green validation
id: validate

View File

@@ -44,8 +44,9 @@ on:
required: false
default: "auto"
type: string
# No secrets: the default publish path is Trusted Publishing (OIDC). The DIRECT
# emergency fallback reads secrets.NPM_TOKEN only on a manual workflow_dispatch.
secrets:
NPM_TOKEN:
required: true
# Least-privilege default: read-only at the top level; each publish job grants the
# id-token (npm provenance) / packages (GitHub Packages) writes it needs (Scorecard
@@ -259,6 +260,10 @@ jobs:
if: steps.resolve.outputs.skip != 'true'
run: git fetch --no-tags --depth=50 origin +refs/heads/main:refs/remotes/origin/main
- name: Validate npm package artifact
if: steps.resolve.outputs.skip != 'true'
run: npm run check:pack-artifact
# Pack ONCE. Up to v3.8.54 this job ran `npm pack` on the same dist/ four times per
# attempt — inside check:pack-boot, inside check:install-upgrade, for the stage-npm
# hand-off and inside the GitHub Packages publish — and `npm pack` is single-threaded:
@@ -266,8 +271,6 @@ jobs:
# 44304134021). Every consumer below now uses this one file, so the bytes the gates
# boot are byte-for-byte the bytes stage-npm publishes; the sha256 recorded here is
# re-checked before the upload and again in stage-npm after the download.
# It runs BEFORE the pack-artifact validation (#20644), so that gate checks this file
# instead of a second `npm pack --dry-run` of its own (12-22 min on the v3.8.54 runs).
- name: Pack the release tarball once
id: pack
if: steps.resolve.outputs.skip != 'true'
@@ -279,7 +282,7 @@ jobs:
rm -f "$TARBALL"
STARTED=$(date +%s)
# --ignore-scripts: prepublishOnly would re-run build:cli-api && build:cli,
# rebuilding bytes this job has already built.
# rebuilding bytes this job has already built and validated.
npm pack --ignore-scripts
test -f "$TARBALL" || { echo "expected $TARBALL to exist after npm pack" >&2; ls -la ./*.tgz || true; exit 1; }
SHA256=$(sha256sum "$TARBALL" | cut -d' ' -f1)
@@ -289,17 +292,6 @@ jobs:
echo "sha256=$SHA256"
} >> "$GITHUB_OUTPUT"
# Validates the tarball packed above (OMNIROUTE_PACKED_TARBALL, #20644): its own file
# list, packed size (the PACK_ARTIFACT_MAX_PACKED_BYTES budget), required runtime
# paths, MCP closure, leaked tests, locale catalog chunks, package.json name/version
# and dist/BUILD_SHA provenance — the bytes that are booted and published, not a
# second dry-run pack. Without the variable the gate still packs the tree itself.
- name: Validate npm package artifact
if: steps.resolve.outputs.skip != 'true'
env:
OMNIROUTE_PACKED_TARBALL: ${{ steps.pack.outputs.path }}
run: npm run check:pack-artifact
- name: Generate CycloneDX SBOM (npm)
if: steps.resolve.outputs.skip != 'true'
run: npx @cyclonedx/cyclonedx-npm --ignore-npm-errors --output-format JSON --output-file sbom-npm.cdx.json
@@ -388,7 +380,7 @@ jobs:
# hosted one (16 GB is not enough for build:cli's next-build fallback — see
# this job's runs-on comment). So this job proves the bytes and hands them
# over; a tiny hosted job does the upload. No re-pack: the file handed over is the
# one packed once above, validated by check:pack-artifact and proven by both gates.
# one packed after "Validate npm package artifact" and proven by both gates above.
- name: Confirm the proven tarball is unchanged before the hand-off
if: steps.resolve.outputs.skip != 'true'
env:
@@ -581,7 +573,8 @@ jobs:
with:
persist-credentials: false
fetch-depth: 0
# Full history needed for auto-bump: git diff against previous release tag
# Full history needed for auto-bump: git diff against the commit npm last published
# the plugin from (its gitHead), or the previous release tag
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
@@ -623,20 +616,49 @@ jobs:
exit 0
fi
# 2) Find the previous release tag (exclude the current one)
PREV_TAG=$(git tag -l 'v*' --sort=-version:refname \
| grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
if [ -z "$PREV_TAG" ]; then
echo "No previous tag to compare — skipping bump."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
# 2) Baseline: the commit npm recorded (gitHead) for the version its "latest" tag
# serves. The previous release tag alone missed a change from a release whose plugin
# publish failed or never ran: the next release already had it at its previous tag,
# saw no diff, and the change never reached npm. git diff compares trees, so the
# commit only has to be in this full-history checkout (fetch-depth: 0), not be an
# ancestor of the release. Without a usable gitHead the previous release tag is the
# baseline, as before; a registry failure fails the step, like npm_has_version.
HEAD_ERR=$(mktemp)
HEAD_RC=0
PUBLISHED_HEAD=$(npm view "${PKG_NAME}@latest" gitHead 2>"$HEAD_ERR") || HEAD_RC=$?
if [ "$HEAD_RC" -ne 0 ]; then
echo "::error::npm view ${PKG_NAME}@latest gitHead failed (exit $HEAD_RC)." >&2
cat "$HEAD_ERR" >&2
exit 1
fi
rm -f "$HEAD_ERR"
BASE=""
if [ -z "$PUBLISHED_HEAD" ]; then
echo "::warning::npm has no gitHead for ${PKG_NAME}@latest — comparing with the previous release tag."
elif [[ ! "$PUBLISHED_HEAD" =~ ^[0-9a-f]{40}$ ]]; then
echo "::warning::npm's gitHead for ${PKG_NAME}@latest is not a commit id — comparing with the previous release tag."
elif ! git cat-file -e "${PUBLISHED_HEAD}^{commit}" 2>/dev/null; then
echo "::warning::${PKG_NAME}@latest was published from ${PUBLISHED_HEAD}, which this checkout does not have — comparing with the previous release tag."
else
BASE="$PUBLISHED_HEAD"
echo "Baseline: ${PKG_NAME}@latest was published from ${BASE}."
fi
if [ -z "$BASE" ]; then
# Previous release tag (exclude the current one)
BASE=$(git tag -l 'v*' --sort=-version:refname \
| grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
if [ -z "$BASE" ]; then
echo "No previous tag to compare — skipping bump."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
fi
# 3) Check if plugin dir actually changed since that tag. The step runs inside the
# plugin folder and git resolves pathspecs against the current directory, so the
# 3) Check if plugin dir actually changed since that baseline. The step runs inside
# the plugin folder and git resolves pathspecs against the current directory, so the
# folder is "." here (the repo-root path matched nothing and no change was ever seen).
if git diff --quiet "$PREV_TAG" -- .; then
echo "⏭️ No plugin changes since $PREV_TAG — nothing to publish."
if git diff --quiet "$BASE" -- .; then
echo "⏭️ No plugin changes since $BASE — nothing to publish."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
@@ -707,7 +729,8 @@ jobs:
with:
persist-credentials: false
fetch-depth: 0
# Full history needed for auto-bump: git diff against previous release tag
# Full history needed for auto-bump: git diff against the commit npm last published
# the plugin from (its gitHead), or the previous release tag
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
@@ -749,20 +772,49 @@ jobs:
exit 0
fi
# 2) Find the previous release tag (exclude the current one)
PREV_TAG=$(git tag -l 'v*' --sort=-version:refname \
| grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
if [ -z "$PREV_TAG" ]; then
echo "No previous tag to compare — skipping bump."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
# 2) Baseline: the commit npm recorded (gitHead) for the version its "latest" tag
# serves. The previous release tag alone missed a change from a release whose plugin
# publish failed or never ran: the next release already had it at its previous tag,
# saw no diff, and the change never reached npm. git diff compares trees, so the
# commit only has to be in this full-history checkout (fetch-depth: 0), not be an
# ancestor of the release. Without a usable gitHead the previous release tag is the
# baseline, as before; a registry failure fails the step, like npm_has_version.
HEAD_ERR=$(mktemp)
HEAD_RC=0
PUBLISHED_HEAD=$(npm view "${PKG_NAME}@latest" gitHead 2>"$HEAD_ERR") || HEAD_RC=$?
if [ "$HEAD_RC" -ne 0 ]; then
echo "::error::npm view ${PKG_NAME}@latest gitHead failed (exit $HEAD_RC)." >&2
cat "$HEAD_ERR" >&2
exit 1
fi
rm -f "$HEAD_ERR"
BASE=""
if [ -z "$PUBLISHED_HEAD" ]; then
echo "::warning::npm has no gitHead for ${PKG_NAME}@latest — comparing with the previous release tag."
elif [[ ! "$PUBLISHED_HEAD" =~ ^[0-9a-f]{40}$ ]]; then
echo "::warning::npm's gitHead for ${PKG_NAME}@latest is not a commit id — comparing with the previous release tag."
elif ! git cat-file -e "${PUBLISHED_HEAD}^{commit}" 2>/dev/null; then
echo "::warning::${PKG_NAME}@latest was published from ${PUBLISHED_HEAD}, which this checkout does not have — comparing with the previous release tag."
else
BASE="$PUBLISHED_HEAD"
echo "Baseline: ${PKG_NAME}@latest was published from ${BASE}."
fi
if [ -z "$BASE" ]; then
# Previous release tag (exclude the current one)
BASE=$(git tag -l 'v*' --sort=-version:refname \
| grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
if [ -z "$BASE" ]; then
echo "No previous tag to compare — skipping bump."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
fi
# 3) Check if plugin-v2 dir actually changed since that tag. The step runs inside the
# plugin folder and git resolves pathspecs against the current directory, so the
# 3) Check if plugin-v2 dir actually changed since that baseline. The step runs inside
# the plugin folder and git resolves pathspecs against the current directory, so the
# folder is "." here (the repo-root path matched nothing and no change was ever seen).
if git diff --quiet "$PREV_TAG" -- .; then
echo "⏭️ No plugin-v2 changes since $PREV_TAG — nothing to publish."
if git diff --quiet "$BASE" -- .; then
echo "⏭️ No plugin-v2 changes since $BASE — nothing to publish."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
@@ -821,129 +873,3 @@ jobs:
fi
npm publish --provenance --access public --ignore-scripts
echo "✅ Published ${PKG_NAME}@${PKG_VERSION}"
publish-opencode-provider:
runs-on: ubuntu-latest
permissions:
contents: read
id-token: write # npm provenance
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
with:
persist-credentials: false
fetch-depth: 0
# Full history needed for auto-bump: git diff against previous release tag
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
node-version: ${{ env.NPM_PUBLISH_NODE_VERSION }}
registry-url: https://registry.npmjs.org
package-manager-cache: false
- name: Auto-bump provider version if provider changed since last release
id: bump
working-directory: "@omniroute/opencode-provider"
env:
CURRENT_TAG: ${{ github.ref_name }}
run: |
set -euo pipefail
PKG_VERSION=$(node -p "require('./package.json').version")
PKG_NAME=$(node -p "require('./package.json').name")
# Exit 0 when npm has ${PKG_NAME}@$1, 1 when it definitely does not (no output, or
# npm's E404). Any other answer is a registry failure: it fails the step instead of
# reading as "not published" (the `npm view ... || true` it replaces did).
npm_has_version() {
local out err rc=0
err=$(mktemp)
out=$(npm view "${PKG_NAME}@$1" version 2>"$err") || rc=$?
if [ "$rc" -eq 0 ] && [ "$out" = "$1" ]; then rm -f "$err"; return 0; fi
if [ "$rc" -eq 0 ] && [ -z "$out" ]; then rm -f "$err"; return 1; fi
if [ "$rc" -ne 0 ] && grep -q 'code E404' "$err"; then rm -f "$err"; return 1; fi
echo "::error::npm view ${PKG_NAME}@$1 was inconclusive (exit $rc): ${out}" >&2
cat "$err" >&2
exit 1
}
# 1) Skip if current version is not yet published (no bump needed)
if ! npm_has_version "$PKG_VERSION"; then
echo "✅ ${PKG_NAME}@${PKG_VERSION} is new — no bump needed."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
# 2) Find the previous release tag (exclude the current one)
PREV_TAG=$(git tag -l 'v*' --sort=-version:refname \
| grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
if [ -z "$PREV_TAG" ]; then
echo "No previous tag to compare — skipping bump."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
# 3) Check if provider dir actually changed since that tag. The step runs inside the
# plugin folder and git resolves pathspecs against the current directory, so the
# folder is "." here (the repo-root path matched nothing and no change was ever seen).
if git diff --quiet "$PREV_TAG" -- .; then
echo "⏭️ No provider changes since $PREV_TAG — nothing to publish."
echo "bumped=false" >> "$GITHUB_OUTPUT"
exit 0
fi
# 4) Auto-bump the patch version past every version npm already has. The bump only
# exists in this job's workspace (the committed manifest keeps the old version), so a
# later release with plugin changes starts from the same manifest: a single bump
# recomputed a version an earlier release had published, and the publish step below
# skipped it without publishing the change.
# Every candidate is looked up before it can be selected; 50 taken candidates fail.
NEW_VERSION=""
for _ in $(seq 1 50); do
npm version patch --no-git-tag-version --allow-same-version
CANDIDATE=$(node -p "require('./package.json').version")
if ! npm_has_version "$CANDIDATE"; then
NEW_VERSION="$CANDIDATE"
break
fi
echo "${PKG_NAME}@${CANDIDATE} is already on npm — bumping again."
done
if [ -z "$NEW_VERSION" ]; then
echo "::error::${PKG_NAME}: no unpublished patch version within 50 bumps of ${PKG_VERSION}."
exit 1
fi
echo "bumped=true" >> "$GITHUB_OUTPUT"
echo "📦 Auto-bumped ${PKG_NAME} from ${PKG_VERSION} to ${NEW_VERSION}"
- name: Install provider dependencies
working-directory: "@omniroute/opencode-provider"
run: npm install --no-audit --no-fund
- name: Build provider
working-directory: "@omniroute/opencode-provider"
run: npm run clean && npm run build
- name: Test provider
working-directory: "@omniroute/opencode-provider"
run: npm test
# Trusted Publishing (OIDC), like the plugins: no NODE_AUTH_TOKEN. The package needs its
# own Trusted Publisher on npmjs.com (cheaper-inference/OmniRoute, npm-publish.yml, no
# environment, "npm publish" allowed); without it this step answers E404 and only this
# job fails — no other publish job depends on it. Until 2026-11 the provider had no
# publish job at all: 0.1.0 was published by hand in 2026-05.
- name: Publish @omniroute/opencode-provider to npm
working-directory: "@omniroute/opencode-provider"
run: |
set -euo pipefail
PKG_VERSION=$(node -p "require('./package.json').version")
PKG_NAME=$(node -p "require('./package.json').name")
# Same hardened skip-check as the main job (no --silent flag).
PUBLISHED="$(npm view "${PKG_NAME}@${PKG_VERSION}" version 2>/dev/null || true)"
if [ "$PUBLISHED" = "$PKG_VERSION" ]; then
echo "⚠️ ${PKG_NAME}@${PKG_VERSION} is already published on npm — skipping."
exit 0
fi
npm publish --provenance --access public --ignore-scripts
echo "✅ Published ${PKG_NAME}@${PKG_VERSION}"

18534
.i18n-state.json generated

File diff suppressed because it is too large Load Diff

View File

@@ -1,53 +1,122 @@
# Mergify — merge queue RETIRED by the owner's decision of 2026-11-19.
# Mergify merge queue — WS3.4/D5 of the v3.8.49 quality/velocity master plan.
#
# History: the Mergify `release` queue (WS3.4/D5 of the v3.8.49 quality/velocity master plan:
# owner-applied `queue` label, serial squash, checks_timeout 240 min) and the opt-in
# `relay-integration` queue landed release PRs until 2026-11-19 (last Mergify merge: #19538,
# 2026-11-15). Their rules, and the rule that removed the `queue` label after a merge, are in
# git history. Release PRs are now merged by hand under the repository ruleset "Require green
# gates on the active release" (`Gate / CI` + `Gate / Quality`) until omni-queue runs in live
# mode, and through omni-queue after that (docs/ops/OMNI_QUEUE.md).
# WHY: ~85-100 active PR authors/month and 300+ PRs/week peaks, all merged by ONE
# identity. The manual merge-train validated batches by hand; this queue automates
# it with batching + automatic batch bisection (a red batch of N costs ~log2(N)
# revalidations instead of N). Mergify Open Source plan: free, unlimited, public repo.
#
# WHY this file is kept instead of deleted: the Mergify GitHub App is still installed, and
# Mergify documents that "With no Mergify configuration, your queue already ... Merges
# automatically when your required checks pass" once someone comments `@mergifyio queue`
# (docs.mergify.com/merge-queue/setup). The docs do not say what that command does on a config
# without `queue_rules`, so the commands that would merge or rewrite a pull request are
# refused here: each condition list below is `closed` AND `-closed`, which no pull request can
# match. `commands_restrictions` is read whatever Mergify products are enabled
# (docs.mergify.com/configuration/file-format). `refresh` and `dequeue` keep their defaults:
# they neither merge nor push.
#
# Contract: tests/unit/mergify-queue-config.test.ts. Do not add `queue_rules`,
# `merge_protections_settings` or a merging `pull_request_rules` action back: two queues would
# act on the same release PRs.
# GOVERNANCE (non-negotiable, mirrors CLAUDE.md Hard Rules #21/#22 + the owner's
# pre-merge ⭐ gate):
# • A PR enters the queue ONLY via the `queue` label — applied by the owner (or a
# session acting for the owner) AFTER the pre-merge ⭐ report/decision. The label
# IS the merge approval; Mergify only executes it.
# • During a release-freeze (open issue labeled `release-freeze`), do NOT label PRs
# targeting the frozen branch — the freeze is a human-honored coordination signal
# the queue cannot see. Retarget to the active release/vX+1 first (Hard Rule #21).
# • Never label a PR another session is actively working (Hard Rule #22b).
# • Fallback path if Mergify misbehaves or the OSS plan changes: the manual
# merge-train runbook (docs/ops/MERGE_TRAIN.md) — remove labels, proceed by hand.
commands_restrictions:
queue:
# Auto-enqueue (current Mergify model, 2026): auto_merge_conditions in
# merge_protections_settings — the rules-based queue action / autoqueue path is
# deprecated (EOL 2026-07-16). The owner-applied `queue` label IS the approval.
merge_protections_settings:
auto_merge_conditions:
- label = queue
queue_rules:
- name: release
# Any current or future release branch — the reason GitHub's native queue was
# rejected (no wildcard support on personal-account repos).
queue_conditions:
- base~=^release/v\d+\.\d+\.\d+$
- label=queue
- -draft
- -conflict
# A reviewed integration candidate must never be squashed by this queue,
# including when its second approval label is missing or its ref changed.
- -label=integration-reviewed
- -head~=^fix/relay-integration-candidate-
# "Everything that ran is green, nothing still running, AND the always-on
# anchor check succeeded" — robust to the path-filtered fast-gates (docs-only
# PRs skip code jobs; matrix shard names vary) while never fail-open: a PR with
# zero checks cannot vacuously merge, because `Merge integrity` runs on EVERY
# non-draft PR (quality.yml) and must be an affirmative success. Review approval
# is intentionally NOT a condition here: the owner-applied `queue` label IS the
# approval in this repo's single-maintainer model (see governance header).
merge_conditions:
# "Zero failures" — EXCEPT the advisory "Build (advisory)" job (quality.yml):
# continue-on-error by design, and its GH-hosted Turbopack build hangs
# recurrently mid-"Creating an optimized production build" (100% failure rate
# across every sampled PR since the job was added 2026-07-27, always killed by
# a runner timeout/shutdown signal, never a real compile error). Any OTHER
# failure still blocks (anti-fail-open kept). The prior dast-smoke exception
# (#7225) was dropped here: dast-smoke's hang (#7226) has been dormant for
# weeks (0 failures in the last 30 runs; 2 all-time, none since 2026-07-13) —
# carrying its tolerance forward would mask problems it no longer causes.
- or:
- "#check-failure=0"
- and:
- "#check-failure=1"
- check-failure=Build (advisory)
- "#check-pending=0"
- "#check-success>=1"
- check-success=Merge integrity (changelog + generated skills)
- check-success=Gate / CI
- check-success=Gate / Quality
# NO batching: 'Merge Queue Batch' requires a paid Mergify tier (live finding
# 2026-07-15 — the queue command fails with "Cannot use Merge Queue batch" on
# the free plan; #7220). Serial queue (1 PR at a time) still automates the train.
# Rail G11 (v3.8.54) asks for batch_size ~5: it stays BLOCKED on that tier —
# adding batch_size/batch_max_wait_time here would dequeue EVERY PR again. Do not
# re-add them unless the Mergify subscription is upgraded (owner decision).
#
# checks_timeout = 2 x p95 wall-clock of the quality.yml workflow (the fast-gates
# that run on PR -> release/**), measured over the last 100 successful runs
# (2026-09-28 .. 2026-10-08, createdAt -> updatedAt, so runner queueing counts):
# mean 34.5 min · p50 1.8 min · p90 101.0 min · p95 119.75 min · max 468.6 min
# (bimodal: path-filtered docs-only runs ~2 min vs full runs ~72 min median).
# 2 x 119.75 = 239.5 -> rounded up to 240 min. A PR whose checks are still
# pending past this is dequeued instead of blocking the serial queue forever.
# Re-measure with: gh run list --workflow quality.yml --status success
# --limit 100 --json createdAt,updatedAt (contract: tests/unit/mergify-queue-config.test.ts).
checks_timeout: 240 min
# Squash keeps the one-commit-per-PR history the CHANGELOG reconciliation expects.
merge_method: squash
# One already-composed PR, NOT Mergify's paid multi-PR batching feature.
# Activation requires this configuration to land on the default branch first.
# See docs/ops/RELAY_INTEGRATION_QUEUE.md for ownership, admission and readback.
- name: relay-integration
queue_conditions:
- base=release/v3.8.52
- head=fix/relay-integration-candidate-20261015
- author=diegosouzapw
- label=queue
- label=integration-reviewed
- -draft
- -conflict
merge_conditions:
- or:
- "#check-failure=0"
- and:
- "#check-failure=1"
- check-failure=Build (advisory)
- "#check-pending=0"
- "#check-success>=1"
- check-success=Merge integrity (changelog + generated skills)
- check-success=Gate / CI
- check-success=Gate / Quality
checks_timeout: 240 min
# Preserve the reviewed original PR heads; rebasing or squash would lose them.
update_method: merge
merge_method: merge
pull_request_rules:
- name: clean up the queue label after merge
conditions:
- closed
- -closed
requeue:
conditions:
- closed
- -closed
rebase:
conditions:
- closed
- -closed
update:
conditions:
- closed
- -closed
squash:
conditions:
- closed
- -closed
backport:
conditions:
- closed
- -closed
copy:
conditions:
- closed
- -closed
- merged
actions:
label:
remove:
- queue

View File

@@ -1,12 +1,12 @@
{
"name": "@omniroute/opencode-provider",
"version": "0.1.1",
"version": "0.1.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@omniroute/opencode-provider",
"version": "0.1.1",
"version": "0.1.0",
"license": "MIT",
"devDependencies": {
"@types/node": "^22.19.19",

View File

@@ -1,6 +1,6 @@
{
"name": "@omniroute/opencode-provider",
"version": "0.1.1",
"version": "0.1.0",
"description": "DEPRECATED — use @omniroute/opencode-plugin instead (it fetches the live OmniRoute /v1/models catalog at startup, so models never drift). This static-config generator still works but is no longer the recommended path. OpenCode provider helper for the OmniRoute AI Gateway.",
"type": "module",
"main": "./dist/index.cjs",

View File

@@ -1,6 +1,6 @@
MIT License
Copyright (c) 2026 Cheaper Inference - Created by Diego Souza https://github.com/diegosouzapw
Copyright (c) 2026 diegosouzapw
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal

View File

@@ -1325,7 +1325,7 @@ Métricas canônicas em 2026-10-18: **1.976 vídeos únicos** · **20.220.289 vi
<tr><td nowrap><b>Runtime</b></td><td>Node.js 22.x / 24.x LTS — <code>&gt;=22.22.2 &lt;23 || &gt;=24.0.0 &lt;27</code></td></tr>
<tr><td nowrap><b>Language</b></td><td>TypeScript 6.0 — <b>100% TypeScript</b> across <code>src/</code> and <code>open-sse/</code> (zero <code>any</code> in core since v2.0)</td></tr>
<tr><td nowrap><b>Framework</b></td><td>Next.js 16 + React 19 + Tailwind CSS 4</td></tr>
<tr><td nowrap><b>Database</b></td><td>better-sqlite3 (SQLite, WAL journaling) + LowDB (JSON legacy) — 147 domain modules, 244 migrations</td></tr>
<tr><td nowrap><b>Database</b></td><td>better-sqlite3 (SQLite, WAL journaling) + LowDB (JSON legacy) — 147 domain modules, 240 migrations</td></tr>
<tr><td nowrap><b>Memory</b></td><td>SQLite FTS5 full-text + int8-quantized vector embeddings, typed decay</td></tr>
<tr><td nowrap><b>Schemas</b></td><td>Zod 4 — MCP tool I/O validation + API contracts</td></tr>
<tr><td nowrap><b>Protocols</b></td><td>MCP (stdio / HTTP / SSE) + A2A v0.3 (JSON-RPC 2.0 + SSE)</td></tr>

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} ይደረግ ነበር",
"cancelled": "ተሰርዟል።",
"jsonOpt": "ውጤቱን እንደ JSON አቅርብ",
"yesOpt": "የማረጋገጫ ጥያቄውን ዝለል",
"positiveIntegerRequired": "ገደቡ አዎንታዊ ኢንቲጀር መሆን አለበት።"
"yesOpt": "የማረጋገጫ ጥያቄውን ዝለል"
},
"setup": {
"title": "የOmniRoute ማዋቀር",

View File

@@ -12,8 +12,7 @@
"dryRun": "[محاكاة] سيتم: {action}",
"cancelled": "تم الإلغاء.",
"jsonOpt": "إخراج بتنسيق JSON",
"yesOpt": "تخطي رسالة التأكيد",
"positiveIntegerRequired": "يجب أن يكون الحد عددًا صحيحًا موجبًا."
"yesOpt": "تخطي رسالة التأكيد"
},
"setup": {
"title": "إعداد OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulyasiya] ediləcəkdi: {action}",
"cancelled": "Ləğv edildi.",
"jsonOpt": "JSON formatında çıxış",
"yesOpt": "Təsdiq sorğusunu keç",
"positiveIntegerRequired": "Limit müsbət tam ədəd olmalıdır."
"yesOpt": "Təsdiq sorğusunu keç"
},
"setup": {
"title": "OmniRoute Quraşdırılması",

View File

@@ -12,8 +12,7 @@
"dryRun": "[симулация] ще извърши: {action}",
"cancelled": "Отменено.",
"jsonOpt": "Изход като JSON",
"yesOpt": "Пропускане на потвърждение",
"positiveIntegerRequired": "Ограничението трябва да е положително цяло число."
"yesOpt": "Пропускане на потвърждение"
},
"setup": {
"title": "Настройка на OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} করা হতো",
"cancelled": "বাতিল করা হয়েছে।",
"jsonOpt": "JSON হিসেবে আউটপুট দিন",
"yesOpt": "নিশ্চিতকরণের প্রম্পট এড়িয়ে যান",
"positiveIntegerRequired": "সীমা একটি ধনাত্মক পূর্ণসংখ্যা হতে হবে।"
"yesOpt": "নিশ্চিতকরণের প্রম্পট এড়িয়ে যান"
},
"setup": {
"title": "OmniRoute সেটআপ",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] bi izvršio {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Izlaz kao JSON",
"yesOpt": "Preskoči potvrdu",
"positiveIntegerRequired": "Limit mora biti pozitivan cijeli broj."
"yesOpt": "Preskoči potvrdu"
},
"setup": {
"title": "OmniRoute Setup",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulace] by provedlo: {action}",
"cancelled": "Zrušeno.",
"jsonOpt": "Výstup jako JSON",
"yesOpt": "Přeskočit potvrzení",
"positiveIntegerRequired": "Limit musí být kladné celé číslo."
"yesOpt": "Přeskočit potvrzení"
},
"setup": {
"title": "Nastavení OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Annulleret.",
"jsonOpt": "Output som JSON",
"yesOpt": "Spring bekræftelse over",
"positiveIntegerRequired": "Grænse skal være et positivt heltal."
"yesOpt": "Spring bekræftelse over"
},
"setup": {
"title": "Opsætning af OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[Simulation] würde: {action}",
"cancelled": "Abgebrochen.",
"jsonOpt": "Ausgabe als JSON",
"yesOpt": "Bestätigung überspringen",
"positiveIntegerRequired": "Der Grenzwert muss eine positive ganze Zahl sein."
"yesOpt": "Bestätigung überspringen"
},
"setup": {
"title": "OmniRoute-Einrichtung",

View File

@@ -12,8 +12,7 @@
"dryRun": "[δοκιμαστική εκτέλεση] θα {action}",
"cancelled": "Ακυρώθηκε.",
"jsonOpt": "Έξοδος ως JSON",
"yesOpt": "Παράλειψη προτροπής επιβεβαίωσης",
"positiveIntegerRequired": "Το όριο πρέπει να είναι θετικός ακέραιος."
"yesOpt": "Παράλειψη προτροπής επιβεβαίωσης"
},
"setup": {
"title": "Εγκατάσταση OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulación] haría: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Salida como JSON",
"yesOpt": "Omitir confirmación",
"positiveIntegerRequired": "El límite debe ser un número entero positivo."
"yesOpt": "Omitir confirmación"
},
"setup": {
"title": "Configuración de OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[testkäivitus] tehakse {action}",
"cancelled": "Tühistatud.",
"jsonOpt": "Väljund JSON-formaadis",
"yesOpt": "Jäta kinnitusküsimus vahele",
"positiveIntegerRequired": "Limiit peab olema positiivne täisarv."
"yesOpt": "Jäta kinnitusküsimus vahele"
},
"setup": {
"title": "OmniRoute seadistus",

View File

@@ -12,8 +12,7 @@
"dryRun": "[شبیه‌سازی] اقدام می‌شد: {action}",
"cancelled": "لغو شد.",
"jsonOpt": "خروجی به صورت JSON",
"yesOpt": "رد کردن تأیید",
"positiveIntegerRequired": "حد باید یک عدد صحیح مثبت باشد."
"yesOpt": "رد کردن تأیید"
},
"setup": {
"title": "راهاندازی OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulointi] tekisi: {action}",
"cancelled": "Peruutettu.",
"jsonOpt": "Tulosta JSON-muodossa",
"yesOpt": "Ohita vahvistuspyyntö",
"positiveIntegerRequired": "Rajan on oltava positiivinen kokonaisluku."
"yesOpt": "Ohita vahvistuspyyntö"
},
"setup": {
"title": "OmniRoute-asennus",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulation] ferait : {action}",
"cancelled": "Annulé.",
"jsonOpt": "Sortie au format JSON",
"yesOpt": "Ignorer la confirmation",
"positiveIntegerRequired": "La limite doit être un entier positif."
"yesOpt": "Ignorer la confirmation"
},
"setup": {
"title": "Configuration d’OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[triail thuras] dhéanfadh {action}",
"cancelled": "Cealaithe.",
"jsonOpt": "Aschur mar JSON",
"yesOpt": "Scipeáil an契ordheimhniú",
"positiveIntegerRequired": "Ní mór teorainn a bheith ina slánuimhir dhearfach."
"yesOpt": "Scipeáil an契ordheimhniú"
},
"setup": {
"title": "Socrú OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} કરાશે",
"cancelled": "રદ કરવામાં આવ્યું.",
"jsonOpt": "JSON તરીકે આઉટપુટ કરો",
"yesOpt": "પુષ્ટિકરણ પ્રોમ્પ્ટ છોડો",
"positiveIntegerRequired": "મર્યાદા સકારાત્મક પૂર્ણાંક હોવી જોઈએ."
"yesOpt": "પુષ્ટિકરણ પ્રોમ્પ્ટ છોડો"
},
"setup": {
"title": "OmniRoute સેટઅપ",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] za a {action}",
"cancelled": "An soke.",
"jsonOpt": "Fitar da sakamako a matsayin JSON",
"yesOpt": "Tsallake tambayar tabbatarwa",
"positiveIntegerRequired": "Dole ne iyakar ta zama cikakkiyar lamba wadda ta fi sifili."
"yesOpt": "Tsallake tambayar tabbatarwa"
},
"setup": {
"title": "Saitin OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[הרצה-יבשה] הפעולה שהייתה מתבצעת: {action}",
"cancelled": "בוטל.",
"jsonOpt": "פלט בפורמט JSON",
"yesOpt": "דילוג על בקשת האישור",
"positiveIntegerRequired": "הגבלה חייבת להיות מספר שלם חיובי."
"yesOpt": "דילוג על בקשת האישור"
},
"setup": {
"title": "הגדרת OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[अनुकरण] करेगा: {action}",
"cancelled": "रद्द किया गया।",
"jsonOpt": "JSON के रूप में आउटपुट",
"yesOpt": "पुष्टि छोड़ें",
"positiveIntegerRequired": "सीमा एक धनात्मक पूर्णांक होनी चाहिए."
"yesOpt": "पुष्टि छोड़ें"
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -12,8 +12,7 @@
"dryRun": "[probni-unos] bi {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Ispis kao JSON",
"yesOpt": "Preskoči upit za potvrdu",
"positiveIntegerRequired": "Ograničenje mora biti pozitivan cijeli broj."
"yesOpt": "Preskoči upit za potvrdu"
},
"setup": {
"title": "OmniRoute Postavljanje",

View File

@@ -12,8 +12,7 @@
"dryRun": "[szimuláció] végrehajtaná: {action}",
"cancelled": "Törölve.",
"jsonOpt": "JSON formátumú kimenet",
"yesOpt": "Megerősítés kihagyása",
"positiveIntegerRequired": "A limitnek pozitív egész számnak kell lennie."
"yesOpt": "Megerősítés kihagyása"
},
"setup": {
"title": "OmniRoute beállítása",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] կկատարվեր՝ {action}",
"cancelled": "Չեղարկված է։",
"jsonOpt": "Արտածել JSON ձևաչափով",
"yesOpt": "Բաց թողնել հաստատման հարցումը",
"positiveIntegerRequired": "Սահմանը պետք է լինի դրական ամբողջ թիվ։"
"yesOpt": "Բաց թողնել հաստատման հարցումը"
},
"setup": {
"title": "OmniRoute-ի կարգավորում",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulasi] akan: {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Keluaran sebagai JSON",
"yesOpt": "Lewati konfirmasi",
"positiveIntegerRequired": "Batas harus berupa bilangan bulat positif."
"yesOpt": "Lewati konfirmasi"
},
"setup": {
"title": "Penyiapan OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] a ga-eme {action}",
"cancelled": "Akagbuola.",
"jsonOpt": "Wepụta dị ka JSON",
"yesOpt": "Mafee ajụjụ nkwenye",
"positiveIntegerRequired": "Oke ga-abụrịrị ọnụọgụ zuru ezu karịrị efu."
"yesOpt": "Mafee ajụjụ nkwenye"
},
"setup": {
"title": "Ntọala OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulazione] eseguirebbe: {action}",
"cancelled": "Annullato.",
"jsonOpt": "Output come JSON",
"yesOpt": "Salta la conferma",
"positiveIntegerRequired": "Il limite deve essere un numero intero positivo."
"yesOpt": "Salta la conferma"
},
"setup": {
"title": "Configurazione di OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[シミュレーション] 実行予定: {action}",
"cancelled": "キャンセルしました。",
"jsonOpt": "JSON形式で出力",
"yesOpt": "確認をスキップ",
"positiveIntegerRequired": "制限は正の整数である必要があります。"
"yesOpt": "確認をスキップ"
},
"setup": {
"title": "OmniRoute セットアップ",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] შესრულდებოდა: {action}",
"cancelled": "გაუქმებულია.",
"jsonOpt": "გამოტანა JSON ფორმატში",
"yesOpt": "დადასტურების მოთხოვნის გამოტოვება",
"positiveIntegerRequired": "ლიმიტი უნდა იყოს დადებითი მთელი რიცხვი."
"yesOpt": "დადასტურების მოთხოვნის გამოტოვება"
},
"setup": {
"title": "OmniRoute-ის დაყენება",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] នឹង {action}",
"cancelled": "បានបោះបង់។",
"jsonOpt": "បញ្ចេញលទ្ធផលជា JSON",
"yesOpt": "រំលងសារស្នើឱ្យបញ្ជាក់",
"positiveIntegerRequired": "ដែនកំណត់ត្រូវតែជាចំនួនគត់វិជ្ជមាន។"
"yesOpt": "រំលងសារស្នើឱ្យបញ្ជាក់"
},
"setup": {
"title": "ការដំឡើង OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[ಡ್ರೈ-ರನ್] {action} ಮಾಡಲಾಗುತ್ತಿತ್ತು",
"cancelled": "ರದ್ದುಗೊಳಿಸಲಾಗಿದೆ.",
"jsonOpt": "JSON ಆಗಿ ಔಟ್ಪುಟ್ ಮಾಡಿ",
"yesOpt": "ದೃಢೀಕರಣ ಪ್ರಾಂಪ್ಟ್ ಅನ್ನು ಬಿಟ್ಟುಬಿಡಿ",
"positiveIntegerRequired": "ಮಿತಿಯು ಧನಾತ್ಮಕ ಪೂರ್ಣಾಂಕವಾಗಿರಬೇಕು."
"yesOpt": "ದೃಢೀಕರಣ ಪ್ರಾಂಪ್ಟ್ ಅನ್ನು ಬಿಟ್ಟುಬಿಡಿ"
},
"setup": {
"title": "OmniRoute ಸೆಟಪ್",

View File

@@ -12,8 +12,7 @@
"dryRun": "[시뮬레이션] 실행 예정: {action}",
"cancelled": "취소되었습니다.",
"jsonOpt": "JSON으로 출력",
"yesOpt": "확인 건너뛰기",
"positiveIntegerRequired": "한도는 양의 정수여야 합니다."
"yesOpt": "확인 건너뛰기"
},
"setup": {
"title": "OmniRoute 설정",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] būtų atliktas veiksmas: {action}",
"cancelled": "Atšaukta.",
"jsonOpt": "Išvesti JSON formatu",
"yesOpt": "Praleisti patvirtinimo užklausą",
"positiveIntegerRequired": "Riba turi būti teigiamas sveikasis skaičius."
"yesOpt": "Praleisti patvirtinimo užklausą"
},
"setup": {
"title": "OmniRoute sąranka",

View File

@@ -12,8 +12,7 @@
"dryRun": "[testrežīms] veiktu {action}",
"cancelled": "Atcelts.",
"jsonOpt": "Izvade JSON formātā",
"yesOpt": "Izlaist apstiprinājuma pieprasījumu",
"positiveIntegerRequired": "Ierobežojumam ir jābūt pozitīvam veselam skaitlim."
"yesOpt": "Izlaist apstiprinājuma pieprasījumu"
},
"setup": {
"title": "OmniRoute iestatīšana",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} ചെയ്യുമായിരുന്നു",
"cancelled": "റദ്ദാക്കി.",
"jsonOpt": "JSON ആയി ഔട്ട്പുട്ട് ചെയ്യുക",
"yesOpt": "സ്ഥിരീകരണ നിർദ്ദേശം ഒഴിവാക്കുക",
"positiveIntegerRequired": "പരിധി ഒരു പോസിറ്റീവ് പൂർണ്ണസംഖ്യയായിരിക്കണം."
"yesOpt": "സ്ഥിരീകരണ നിർദ്ദേശം ഒഴിവാക്കുക"
},
"setup": {
"title": "OmniRoute സജ്ജീകരണം",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} केले असते",
"cancelled": "रद्द केले.",
"jsonOpt": "JSON स्वरूपात आउटपुट द्या",
"yesOpt": "पुष्टीकरण प्रॉम्प्ट वगळा",
"positiveIntegerRequired": "मर्यादा सकारात्मक पूर्णांक असणे आवश्यक आहे."
"yesOpt": "पुष्टीकरण प्रॉम्प्ट वगळा"
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] akan {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Output sebagai JSON",
"yesOpt": "Langkau gesaan pengesahan",
"positiveIntegerRequired": "Had mestilah integer positif."
"yesOpt": "Langkau gesaan pengesahan"
},
"setup": {
"title": "Persediaan OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] se jaġixx {action}",
"cancelled": "Kkanċellat.",
"jsonOpt": "Output bħala JSON",
"yesOpt": "Qabżu l-prompt ta' konferma",
"positiveIntegerRequired": "Il-limitu għandu jkun numru sħiħ pożittiv."
"yesOpt": "Qabżu l-prompt ta' konferma"
},
"setup": {
"title": "Twaqqif ta' OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} လုပ်ဆောင်မည်",
"cancelled": "ပယ်ဖျက်လိုက်သည်။",
"jsonOpt": "JSON အဖြစ် ထုတ်ပေးရန်",
"yesOpt": "အတည်ပြုချက် တောင်းခံမှုကို ကျော်ရန်",
"positiveIntegerRequired": "ကန့်သတ်ချက်သည် အပေါင်းကိန်းပြည့်ဖြစ်ရမည်။"
"yesOpt": "အတည်ပြုချက် တောင်းခံမှုကို ကျော်ရန်"
},
"setup": {
"title": "OmniRoute စနစ်ထည့်သွင်းခြင်း",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] ले {action} गर्ने थियो",
"cancelled": "रद्द गरियो।",
"jsonOpt": "JSON का रूपमा आउटपुट गर्नुहोस्",
"yesOpt": "पुष्टि प्रम्प्ट छोड्नुहोस्",
"positiveIntegerRequired": "सीमा सकारात्मक पूर्णांक हुनुपर्छ।"
"yesOpt": "पुष्टि प्रम्प्ट छोड्नुहोस्"
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulatie] zou: {action}",
"cancelled": "Geannuleerd.",
"jsonOpt": "Uitvoer als JSON",
"yesOpt": "Bevestiging overslaan",
"positiveIntegerRequired": "Limiet moet een positief geheel getal zijn."
"yesOpt": "Bevestiging overslaan"
},
"setup": {
"title": "OmniRoute-installatie",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Avbrutt.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hopp over bekreftelse",
"positiveIntegerRequired": "Grensen må være et positivt heltall."
"yesOpt": "Hopp over bekreftelse"
},
"setup": {
"title": "Oppsett av OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} କରାଯାଇଥାନ୍ତା",
"cancelled": "ବାତିଲ୍ କରାଗଲା।",
"jsonOpt": "JSON ଭାବେ ଆଉଟ୍‌ପୁଟ୍ କରନ୍ତୁ",
"yesOpt": "ନିଶ୍ଚିତକରଣ ପ୍ରମ୍ପ୍ଟ ଏଡ଼ାନ୍ତୁ",
"positiveIntegerRequired": "ସୀମା ଏକ ସକାରାତ୍ମକ ପୂର୍ଣ୍ଣ ସଂଖ୍ୟା ହେବା ଆବଶ୍ୟକ।"
"yesOpt": "ନିଶ୍ଚିତକରଣ ପ୍ରମ୍ପ୍ଟ ଏଡ଼ାନ୍ତୁ"
},
"setup": {
"title": "OmniRoute ସେଟ୍‌ଅପ୍",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} ਕੀਤਾ ਜਾਵੇਗਾ",
"cancelled": "ਰੱਦ ਕੀਤਾ ਗਿਆ।",
"jsonOpt": "ਆਉਟਪੁੱਟ JSON ਵਜੋਂ ਦਿਓ",
"yesOpt": "ਪੁਸ਼ਟੀਕਰਨ ਪ੍ਰੌਂਪਟ ਛੱਡੋ",
"positiveIntegerRequired": "ਸੀਮਾ ਇੱਕ ਸਕਾਰਾਤਮਕ ਪੂਰਨ ਅੰਕ ਹੋਣੀ ਚਾਹੀਦੀ ਹੈ।"
"yesOpt": "ਪੁਸ਼ਟੀਕਰਨ ਪ੍ਰੌਂਪਟ ਛੱਡੋ"
},
"setup": {
"title": "OmniRoute ਸੈੱਟਅੱਪ",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] isasagawa sana ang {action}",
"cancelled": "Kinansela.",
"jsonOpt": "I-output bilang JSON",
"yesOpt": "Laktawan ang prompt sa pagkumpirma",
"positiveIntegerRequired": "Ang limitasyon ay dapat na isang positibong integer."
"yesOpt": "Laktawan ang prompt sa pagkumpirma"
},
"setup": {
"title": "Pag-setup ng OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[symulacja] wykonałoby: {action}",
"cancelled": "Anulowano.",
"jsonOpt": "Wyjście jako JSON",
"yesOpt": "Pomiń potwierdzenie",
"positiveIntegerRequired": "Limit musi być dodatnią liczbą całkowitą."
"yesOpt": "Pomiń potwierdzenie"
},
"setup": {
"title": "Konfiguracja OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Pular confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
"yesOpt": "Pular confirmação"
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Ignorar confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
"yesOpt": "Ignorar confirmação"
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulare] ar face: {action}",
"cancelled": "Anulat.",
"jsonOpt": "Ieșire ca JSON",
"yesOpt": "Omite confirmarea",
"positiveIntegerRequired": "Limita trebuie să fie un număr întreg pozitiv."
"yesOpt": "Omite confirmarea"
},
"setup": {
"title": "Configurare OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[симуляция] выполнит: {action}",
"cancelled": "Отменено.",
"jsonOpt": "Вывод в формате JSON",
"yesOpt": "Пропустить подтверждение",
"positiveIntegerRequired": "Лимит должен быть положительным целым числом."
"yesOpt": "Пропустить подтверждение"
},
"setup": {
"title": "Настройка OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} කරනු ඇත",
"cancelled": "අවලංගු කරන ලදී.",
"jsonOpt": "JSON ලෙස ප්රතිදානය කරන්න",
"yesOpt": "තහවුරු කිරීමේ විමසුම මඟ හරින්න",
"positiveIntegerRequired": "සීමාව ධන නිඛිලයක් විය යුතුය."
"yesOpt": "තහවුරු කිරීමේ විමසුම මඟ හරින්න"
},
"setup": {
"title": "OmniRoute පිහිටුවීම",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulácia] by vykonalo: {action}",
"cancelled": "Zrušené.",
"jsonOpt": "Výstup ako JSON",
"yesOpt": "Preskočiť potvrdenie",
"positiveIntegerRequired": "Limit musí byť kladné celé číslo."
"yesOpt": "Preskočiť potvrdenie"
},
"setup": {
"title": "Nastavenie OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[poskusni zagon] izvedlo bi se dejanje: {action}",
"cancelled": "Preklicano.",
"jsonOpt": "Izpis v obliki JSON",
"yesOpt": "Preskoči poziv za potrditev",
"positiveIntegerRequired": "Omejitev mora biti pozitivno celo število."
"yesOpt": "Preskoči poziv za potrditev"
},
"setup": {
"title": "Nastavitev OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[пробно покретање] би {action}",
"cancelled": "Отказано.",
"jsonOpt": "Прикажи као JSON",
"yesOpt": "Прескочи потврду",
"positiveIntegerRequired": "Ограничење мора бити позитиван цео број."
"yesOpt": "Прескочи потврду"
},
"setup": {
"title": "OmniRoute подешавање",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simulering] skulle: {action}",
"cancelled": "Avbruten.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hoppa över bekräftelse",
"positiveIntegerRequired": "Gränsen måste vara ett positivt heltal."
"yesOpt": "Hoppa över bekräftelse"
},
"setup": {
"title": "OmniRoute-konfiguration",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] ingefanya {action}",
"cancelled": "Imeghairiwa.",
"jsonOpt": "Toa matokeo kama JSON",
"yesOpt": "Ruka kidokezo cha uthibitishaji",
"positiveIntegerRequired": "Kikomo lazima kiwe nambari kamili chanya."
"yesOpt": "Ruka kidokezo cha uthibitishaji"
},
"setup": {
"title": "Usanidi wa OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} செய்யப்படும்",
"cancelled": "ரத்துசெய்யப்பட்டது.",
"jsonOpt": "JSON ஆக வெளியிடு",
"yesOpt": "உறுதிப்படுத்தல் கேள்வியைத் தவிர்",
"positiveIntegerRequired": "வரம்பு நேர்மறை முழு எண்ணாக இருக்க வேண்டும்."
"yesOpt": "உறுதிப்படுத்தல் கேள்வியைத் தவிர்"
},
"setup": {
"title": "OmniRoute அமைப்பு",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} చేస్తుంది",
"cancelled": "రద్దు చేయబడింది.",
"jsonOpt": "JSONగా అవుట్పుట్ చేయండి",
"yesOpt": "నిర్ధారణ ప్రాంప్ట్ను దాటవేయండి",
"positiveIntegerRequired": "పరిమితి తప్పనిసరిగా ధనాత్మక పూర్ణాంకం అయి ఉండాలి."
"yesOpt": "నిర్ధారణ ప్రాంప్ట్ను దాటవేయండి"
},
"setup": {
"title": "OmniRoute సెటప్",

View File

@@ -12,8 +12,7 @@
"dryRun": "[จำลอง] จะทำ: {action}",
"cancelled": "ยกเลิกแล้ว",
"jsonOpt": "ส่งออกเป็น JSON",
"yesOpt": "ข้ามการยืนยัน",
"positiveIntegerRequired": "ขีดจำกัดต้องเป็นจำนวนเต็มบวก"
"yesOpt": "ข้ามการยืนยัน"
},
"setup": {
"title": "ตั้งค่า OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[simülasyon] yapılacaktı: {action}",
"cancelled": "İptal edildi.",
"jsonOpt": "JSON olarak çıktı",
"yesOpt": "Onayı atla",
"positiveIntegerRequired": "Limit pozitif bir tam sayı olmalıdır."
"yesOpt": "Onayı atla"
},
"setup": {
"title": "OmniRoute Kurulumu",

View File

@@ -12,8 +12,7 @@
"dryRun": "[симуляція] виконає: {action}",
"cancelled": "Скасовано.",
"jsonOpt": "Вивести у форматі JSON",
"yesOpt": "Пропустити підтвердження",
"positiveIntegerRequired": "Ліміт має бути додатним цілим числом."
"yesOpt": "Пропустити підтвердження"
},
"setup": {
"title": "Налаштування OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[آزمائشی اجرا] {action} کیا جاتا",
"cancelled": "منسوخ کر دیا گیا۔",
"jsonOpt": "JSON کی صورت میں آؤٹ پٹ دیں",
"yesOpt": "تصدیقی پیغام کو چھوڑ دیں",
"positiveIntegerRequired": "حد ایک مثبت صحیح عدد ہونی چاہیے۔"
"yesOpt": "تصدیقی پیغام کو چھوڑ دیں"
},
"setup": {
"title": "OmniRoute سیٹ اپ",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] {action} bajarilgan bo‘lardi",
"cancelled": "Bekor qilindi.",
"jsonOpt": "JSON formatida chiqarish",
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish",
"positiveIntegerRequired": "Limit musbat butun son boʻlishi kerak."
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish"
},
"setup": {
"title": "OmniRoute sozlamalari",

View File

@@ -12,8 +12,7 @@
"dryRun": "[mô phỏng] sẽ: {action}",
"cancelled": "Đã hủy.",
"jsonOpt": "Xuất dưới dạng JSON",
"yesOpt": "Bỏ qua xác nhận",
"positiveIntegerRequired": "Giới hạn phải là số nguyên dương."
"yesOpt": "Bỏ qua xác nhận"
},
"setup": {
"title": "Thiết lập OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "[dry-run] yóò {action}",
"cancelled": "A ti fagilé.",
"jsonOpt": "Ṣe àbájáde gẹ́gẹ́ bí JSON",
"yesOpt": "Fo ìbéèrè ìmúdájú",
"positiveIntegerRequired": "Iye ààlà gbọ́dọ̀ jẹ́ odidi nọ́ńbà rere."
"yesOpt": "Fo ìbéèrè ìmúdájú"
},
"setup": {
"title": "Ìṣètò OmniRoute",

View File

@@ -12,8 +12,7 @@
"dryRun": "【模拟】将执行:{action}",
"cancelled": "已取消。",
"jsonOpt": "以 JSON 格式输出",
"yesOpt": "跳过确认",
"positiveIntegerRequired": "限制必须是正整数。"
"yesOpt": "跳过确认"
},
"setup": {
"title": "OmniRoute 设置",

View File

@@ -12,8 +12,7 @@
"dryRun": "【模擬】將執行:{action}",
"cancelled": "已取消。",
"jsonOpt": "以 JSON 格式輸出",
"yesOpt": "跳過確認",
"positiveIntegerRequired": "限制必須是正整數。"
"yesOpt": "跳過確認"
},
"setup": {
"title": "OmniRoute 設定",

View File

@@ -515,8 +515,7 @@ async function pollHealthOnce(port, probeTimeoutMs = INITIAL_PROBE_TIMEOUT_MS) {
const results = await Promise.all(
hosts.map(async (host) => {
try {
const urlHost = host.includes(":") ? `[${host}]` : host;
const res = await fetch(`http://${urlHost}:${port}/api/monitoring/health`, {
const res = await fetch(`http://${host}:${port}/api/monitoring/health`, {
signal: AbortSignal.timeout(probeTimeoutMs),
});
return { host, outcome: res.ok ? "ready" : "fast-reject" };

View File

@@ -1 +0,0 @@
- feat(routing): allow scoping task-aware routing to specific target or excluded models/combos via `targetModels` and `excludedModels` in TaskRoutingConfig (#20294)

View File

@@ -1 +0,0 @@
- Derived documentation refresh now recognizes migration edits already located in translated database rows. It preserves unrelated historical numbers with the same value and requires matching, complete claim identities before refreshing translation state.

View File

@@ -1 +0,0 @@
- Merge verified coverage shards in their original reporting order and write a single aggregate for c8, reducing temporary disk use on CI runners.

View File

@@ -1 +0,0 @@
- **cache**: Do not store upstream refusals, obsolescence notices, or content filter blocks in semantic cache (#19619).

View File

@@ -1 +0,0 @@
- Prevent mid-stream SSE heartbeat timers from growing unread chunk queues without bound on abandoned client connections by checking downstream backpressure and stopping the interval after consecutive unconsumed ticks (#19640).

View File

@@ -1 +0,0 @@
- 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.

View File

@@ -1 +0,0 @@
- Classify OpenRouter request-capability and provider-preference 404 responses (such as "No endpoints found that support image input" or "No allowed providers") as request-scoped failures instead of `MODEL_NOT_FOUND`, preventing an unwarranted 120-second model lockout for all callers (#19686).

View File

@@ -1 +0,0 @@
- **fix(providers):** preserve multi-key JSON payloads and solitary thought objects in Gemini leak filter instead of stripping structured responses to 0 chars ([#19805](https://github.com/cheaper-inference/OmniRoute/issues/19805)) — thanks @ctrindade0503

View File

@@ -1 +0,0 @@
- **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)).

View File

@@ -1 +0,0 @@
- **fix(authz):** include `/:a2aseg([aA]2[aA])` and `/:connectseg([cC][oO][nN][nN][eE][cC][tT])` in the Next.js proxy matcher and classify `/a2a` as `CLIENT_API` while enforcing header-only API key credentials (`allowUrl: false`), ensuring IP filter, route classification, body size guards, and pipeline headers apply consistently ([#19832](https://github.com/cheaper-inference/OmniRoute/issues/19832)).

View File

@@ -1 +0,0 @@
- **fix(telegram):** enforce bidirectional timestamp boundaries on Mini App `initData` and add opt-in replay protection. Previously, future `auth_date` values bypassed the `now - authDate > maxAgeSec` freshness check and never expired. The in-memory replay cache (`TELEGRAM_INITDATA_ANTI_REPLAY=true`, off by default) rejects an exact repeat of an (`initData`, message) pair within the validity window ([#19833](https://github.com/cheaper-inference/OmniRoute/issues/19833)).

View File

@@ -1 +0,0 @@
- **fix(webdav):** add per-IP Basic authentication failure tracking, rate limiting, and lockout (10 attempts in 60s triggers a 5-minute lockout answering 429 with `Retry-After`), along with audit failure logging and transport security guidance ([#19834](https://github.com/cheaper-inference/OmniRoute/issues/19834)).

View File

@@ -1 +0,0 @@
- **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)

View File

@@ -1 +0,0 @@
- **fix(api):** derived model display names drop dash-separated release dates, so `gpt-5-2025-08-07` reads `GPT-5` instead of `GPT-5.2025 08.07`. (fixes #20070) ([#20071](https://github.com/cheaper-inference/OmniRoute/pull/20071))

View File

@@ -1 +0,0 @@
- **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

View File

@@ -1 +0,0 @@
- 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).

View File

@@ -1 +0,0 @@
- **fix(providers):** add Gemini 4 Hydrogen specs, bare id alias, 65k output cap, and pricing rows across Antigravity, Gemini, and Vertex catalogs ([#20124](https://github.com/cheaper-inference/OmniRoute/issues/20124)) — thanks @xiaoyaner0201

View File

@@ -1 +0,0 @@
- **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))

View File

@@ -1 +0,0 @@
- **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))

View File

@@ -1 +0,0 @@
- **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))

View File

@@ -1 +0,0 @@
- 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).

Some files were not shown because too many files have changed in this diff Show More