Commit Graph

19 Commits

Author SHA1 Message Date
Kiaro-Sama
cbc4e48464 fix(ci): verify and require pinned workflow scanners (#19299)
## Summary

- Restore the required workflow audit by installing verified, pinned scanners before the audit in both CI and Quality Gates. Reuse `scripts/ci/install-workflow-scanners.sh` as a required setup step outside the advisory multi-scanner step.
- Download the exact actionlint v1.7.12 Linux amd64 release asset through the authenticated runner GitHub CLI, with at most three attempts. Preserve the pinned SHA-256 verification before extraction and exact version checks before publishing PATH.
- Keep zizmor at 1.25.2 with its existing pinned artifact and checksum. Neither scanner may fall back to a cached/global binary.
- Supply the runner token to both existing Release-Green installer callers while retaining their immutable workflow-revision lookup.

The failure was reproduced in [the #18849 Extended job](https://github.com/cheaper-inference/OmniRoute/actions/runs/42464233885/job/128685771611): the browser download returned HTTP 504, `text/html`, and a 92-byte Gateway Time-out response that tar could not extract. The public release asset API served the archive with the SHA-256 already pinned in the repository. The failed audit correctly reported INCOMPLETE.

No baseline, scanner version, audit assertion, CodeQL alert, or security permission is weakened. This repair is separate from the feature PRs because the installer failure belongs to the release base.

## Related Issues

- Related to #18849: required workflow audit blocked by the shared actionlint download failure.
- Rel

Thanks @KiaroSama.
2026-11-09 04:43:07 -03:00
Diego Rodrigues de Sa e Souza
e7211fcc76 fix(ci): count only jobs a runner took in the Blacksmith budget (#19155)
GitHub fills started_at while a job still waits in the queue, so an
amd64 job stuck for 13 h read as 1,596 spent minutes.
2026-11-05 17:39:16 +00:00
Rouzbeh†
44e201b8ff fix(docker): require amd64 and arm64 for every image variant (#18749)
Merged as part of the v3.8.53 fix sweep (author @rqzbeh).

Co-authored-by: rqzbeh <78313022+rqzbeh@users.noreply.github.com>
Co-authored-by: Diego Rodrigues de Sa e Souza <diegosouza.pw@gmail.com>
2026-11-04 22:27:28 -03:00
Alireza Riahi
535f0724d1 fix(ci): verify patched Node runtimes before Docker publication (#18585)
Merged as part of the v3.8.53 fix sweep (author @alirezariahi).

Co-authored-by: Alireza <ali.r.riahi@gmail.com>
Co-authored-by: Diego Rodrigues de Sa e Souza <diegosouza.pw@gmail.com>
2026-11-04 04:49:19 -03:00
Diego Rodrigues de Sa e Souza
3b8757ac3c feat(ci): fall back to hosted when the Blacksmith monthly minutes run out (#18893)
Blacksmith keeps running and invoices past its free 3,000 minutes, and
a publish costs ~95 of them. prepare now sums the month's Blacksmith
minutes from the workflow's own jobs and routes build and merge to the
hosted runner at BLACKSMITH_MONTHLY_MINUTES_CAP (default 2500).
2026-11-03 18:49:23 -03:00
Diego Rodrigues de Sa e Souza
60519b8c6d ci(dashboard): keep one UI kit sync PR open from the latest upstream release (#18769)
The UI Kit upstream watch only opened a tracking issue, so a new kit release still waited for
someone to run the sync by hand. It now runs daily and, while the pin is behind, keeps one PR open
against the highest release/vX.Y.Z branch through scripts/ci/ui-kit-sync-pr.sh. It never merges:
every kit release still needs a visual check on the local VPS.

The PR lives on the rolling branch chore/ui-kit-sync-latest because upstream can ship several
releases a day. The branch is rebuilt when a newer release is out and left alone otherwise. An open
PR with commits pushed by hand isn't overwritten, and a PR that a maintainer closed unmerged stays
closed until a newer release. The watch holds while the target release is frozen.

When no PR can be opened, the tracking issue says why. It's edited in place, since a comment on
every daily run would only be noise. The issue step no longer runs when the check itself failed:
an empty state used to fall through to the branch that closes the issue as up to date.

Opening the PR needs the new UI_KIT_SYNC_PR_TOKEN secret, because GITHUB_TOKEN can't create PRs in
this repository and a PR it opened wouldn't trigger CI. Without it only the branch is pushed.
2026-11-03 10:17:23 -03:00
Diego Rodrigues de Sa e Souza
3d2349326c fix(ci): reject incomplete release workflow audits (#17412)
The Release-Green observer and its report verifier treat a missing or broken workflow scanner as incomplete evidence instead of nonblocking drift.

Evidence: focused tests passed on a combined board (build/release-green-workflow-evidence.test.ts); lint, typecheck:core and check-deps OK; open-sse-typecheck OK; api-typecheck reports only errors in files this batch does not touch, reproduced on the pure tip; file-size OK; changelog integrity OK against origin/release/v3.8.53.

⚠️ base-red inherited: #17219
2026-10-31 22:15:21 -03:00
Diego Rodrigues de Sa e Souza
2c4e3ab7aa fix(release): drain the deterministic unit and vitest reds of release/v3.8.53 (#18426) 2026-10-28 08:48:59 -03:00
Diego Rodrigues de Sa e Souza
0bd2a757b9 ci: cancel a pull request's queued and running runs when it closes (#18278)
Cancel a pull request's queued and running runs when it closes.

Evidence: focused tests pass (tests/unit/cancel-closed-pr-runs.test.ts); combined board of 6 PRs on origin/release/v3.8.53: 75/75 focused tests, ESLint, typecheck:core, check:open-sse-typecheck and API-route typecheck clean; file-size OK; changelog integrity OK against origin/release/v3.8.53.

⚠️ base-red inherited: #17219
2026-10-27 00:06:36 -03:00
Diego Rodrigues de Sa e Souza
4bc80388a9 fix(ci): bind hosted suite receipts to the exact execution (#17851)
Bind hosted Release-Green suite receipts to the exact execution that produced them.

Evidence: focused tests (tests/unit/build/release-green-hosted-suites.test.ts, tests/unit/build/release-green-suite-provenance.test.mjs, tests/unit/build/release-green-workflow-verdict.test.ts); combined board of 6 PRs on origin/release/v3.8.53 with ESLint, typecheck:core, check:open-sse-typecheck and check-deps clean; file-size OK; changelog integrity OK against origin/release/v3.8.53.

⚠️ base-red inherited: #17219
2026-10-25 22:46:03 -03:00
Diego Rodrigues de Sa e Souza
98874b216f fix(ci): reject dependencies that drift from candidate lockfile (#17854)
Reject CI installs whose dependencies drift from the candidate lockfile.

Evidence: focused tests pass (tests/unit/build/verify-ci-install.test.mjs), validated in one combined board of 9 PRs on origin/release/v3.8.53 with typecheck:core, check:open-sse-typecheck and ESLint clean; file-size OK; changelog integrity OK against origin/release/v3.8.53.

⚠️ base-red inherited: #17219
2026-10-24 23:02:06 -03:00
Diego Rodrigues de Sa e Souza
05d44f9a11 fix(ci): provision verified workflow scanners for release observers (#17846)
Provision verified, pinned scanners for the Release-Green observer jobs.

Evidence: focused tests pass (tests/unit/release-green-scanner-setup.test.mjs), validated in one combined board of 9 PRs on origin/release/v3.8.53 with typecheck:core, check:open-sse-typecheck and ESLint clean; file-size OK; changelog integrity OK against origin/release/v3.8.53.

⚠️ base-red inherited: #17219
2026-10-24 23:01:54 -03:00
Diego Rodrigues de Sa e Souza
0520f9e8b1 ci(release-green): run the sweep's suites on hosted runners, keep the build on the slot (#17350)
Four full sweeps on the 8-core omni-release slot (2026-10-19/20) took ~4h15 each and stayed
red for capacity, not code: unit shards ran 26-40 min against ~13 min hosted, timing tests
failed on CPU starvation (the /v1/models catalog's 8 s build bound answered 503), integration
hit its 40 min ceiling, and the webpack build died with "JavaScript heap out of memory" at
build-next-isolated's 8192 MB default.

Schedule/dispatch now resolve the target commit once (resolve-target), run ci.yml's own unit
and integration shards plus vitest (MCP + UI) as a hosted matrix on that commit (suites), and
the slot job reads their results with --suites-from: the validator folds them into the same
unit/integration/vitest HARD gates, so the verdict, the tracking issue and release-green.json
keep their ids; a job that never reports fails its lane. The slot keeps the static gates and
the package build, which now gets OMNIROUTE_BUILD_MEMORY_MB=12288 (docker-publish's proven
value). Push (--quick) and main-green are unchanged.

Refs #17219
2026-10-21 04:52:24 -03:00
Diego Rodrigues de Sa e Souza
664f9717e4 fix(ci): verify native runtimes before accepting dependency installs (#15781)
Batch-merged with the owner's 2026-10-09 PR wave (/merge-batch). Validated in one combined tree of 57 boarded PRs on top of release/v3.8.52 (35ef635c): typecheck:core, check:open-sse-typecheck, check-deps, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on all 247 changed source files — all green for this wave; 89 focused unit test files (739/744 pass under node:test, the 4 UI .tsx files re-run under vitest 13/13, check-deps fixed in #15912). Remaining reds in that tree belong only to held/draft PRs outside this wave (#15790 file-size, #15780 open-sse types).
2026-10-09 12:44:58 -03:00
Diego Rodrigues de Sa e Souza
e2ffe161e3 fix(ci): enforce exact-SHA release-green evidence and verdicts (#14376)
Validated in a combined board with 8 sibling PRs on release/v3.8.52: typecheck:core, file-size, changelog-integrity and complexity gates green; 13 focused test files, 89/89 passing.
2026-10-01 18:22:18 -03:00
Paco Cartones
eb9b4cec54 fix(ci): skip stale release Docker publishes (#11527)
Validated in a combined 10-PR batch worktree off release/v3.8.51 tip. Fixes #11523.
- Focused test: tests/unit/build/docker-next-channel-8576.test.ts — 7/7 pass
- typecheck:core, file-size, changelog-integrity, complexity, cognitive-complexity gates — all OK
- Full-repo lint: 503 pre-existing problems confirmed identical on the pure release/v3.8.51 tip — unrelated to this diff

⚠️ base-red inherited: #11449

Thanks for treating Docker publishes from non-default frozen release branches as an expected no-op.
2026-08-25 13:12:02 -03:00
rinseaid
1f45cf885c fix(vision): preserve images for text-only routes (#9037)
* fix(vision): preserve images for text-only routes

* fix(i18n): complete Vietnamese vision bridge copy

* fix(ci): drain prerelease tag input

---------

Co-authored-by: rinseaid <rinseaid@rinseaid.net>
2026-08-11 04:30:10 -03:00
Aman
1b2a72ebc8 feat(docker): publish next from active release branches (#9181)
Validated in local merge-train T4 (HouMinXi+Zartharas+Andrian+artickc)
2026-08-05 23:51:50 -03:00
Diego Rodrigues de Sa e Souza
7c23dab64d Release v3.8.40
v3.8.40 cycle integration → main. All test gates green (Unit/Integration/Coverage/Node-compat/Quality-Ratchet). The only red check, 'PR Test Policy', is the test-masking heuristic firing on the cumulative ~57-commit release diff (legitimate assert consolidations already reviewed per-PR — Gemini CLI removal #5246, retired GPT models #5280, provider catalog refreshes); overridden with --admin per the documented release-PR convention. CodeQL/SonarQube advisory scans non-blocking; #5278's code already passed CodeQL on main. Homologated on VPS 192.168.0.15 (v3.8.40 healthy).
2026-06-29 08:40:06 -03:00